TorbatYar/docs/phase-handover/phase-12-3.md
Mortezakoohjani 5c6a2e78cf feat(platform): seed service registry, deploy all modules, and fix homepage catalog.
Register all active platform services and base features in core DB so admin can manage them, add delivery/hospitality/sports-center backend phases, update apps catalog and production deploy tooling.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-27 12:39:51 +03:30

50 lines
1.3 KiB
Markdown

# Phase Handover — 12.3 Table Service & Reservations
## Metadata
| Field | Value |
| --- | --- |
| Phase ID | hospitality-12.3 |
| Title | Table Service & Reservations |
| Status | Complete |
| Service(s) | hospitality |
| Version | 0.12.3.0 |
| Date | 2026-07-26 |
| ADR(s) | ADR-017 (no new ADR) |
## Summary
Reservations, table assignments, in-service requests, and waitlist entries on `hospitality_db`.
All status transitions are shell-only — **no POS/kitchen/payment**.
## Public APIs
| Method | Path |
| --- | --- |
| CRUD/list + status | `/api/v1/reservations`, `/{id}/status` |
| CRUD/list + release | `/api/v1/table-assignments`, `/{id}/release` |
| CRUD/list + status | `/api/v1/service-requests`, `/{id}/status` |
| CRUD/list + status | `/api/v1/waitlist`, `/{id}/status` |
## Events
`hospitality.reservation.created|status_changed`, `table_assignment.created`, `service_request.created`, `waitlist_entry.created`
## Migration
`0004_phase_123_table_service_reservations` (additive)
## Known Limitations
- No POS / kitchen / payment engines
- No automatic table-to-reservation matching engine
- Public unauthenticated guest access not applicable (staff-facing only)
## Next Phase Entry
Phase **12.4 — POS Lite**
## Service Snapshot
Regenerated: `docs/service-snapshots/hospitality.yaml`