Signal Schedule v5.13.0
Backend Readiness
Pre-v6 backend checklist for database migrations, API contracts, repository adapters, and production write safety.
Backend Readiness Checklist
| Area | Status | Notes |
|---|---|---|
| Postgres | Not moved | Existing database can remain in place until live backend wiring. |
| API contracts | Foundation | Contracts exist for many modules and need pre-v6 review. |
| Repositories | Foundation | JSON adapters remain safe for frontend previews. |
| Writes | Disabled | No production publishing, approval, or leave-bank writes yet. |
| Migrations | Staged | Request, leave, approval, staffing, assignment, mandation, and publishing migration order must be locked before v6. |
Decision Before v6.0
Choose whether Schedule reuses the existing Coolify Postgres service or receives a dedicated Signal Schedule database service. No move is required during v5.6.