TorbatYar/docs/phase-handover/phase-12-2.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

49 lines
1.3 KiB
Markdown

# Phase Handover — 12.2 QR Menu & QR Ordering
## Metadata
| Field | Value |
| --- | --- |
| Phase ID | hospitality-12.2 |
| Title | QR Menu & QR Ordering |
| Status | Complete |
| Service(s) | hospitality |
| Version | 0.12.2.0 |
| Date | 2026-07-26 |
| ADR(s) | ADR-017 (no new ADR) |
## Summary
QR codes, guest menu sessions, ordering sessions, and cart/line shells on `hospitality_db`. Submit is status-only — **no POS/kitchen/payment**.
## Public APIs
| Method | Path |
| --- | --- |
| CRUD/list | `/api/v1/qr-codes`, `/by-token/{token}` |
| CRUD/list | `/api/v1/qr-menu-sessions`, `/by-token/{token}` |
| CRUD + submit | `/api/v1/qr-ordering-sessions`, `/{id}/submit` |
| CRUD | `/api/v1/carts`, `/api/v1/cart-lines` |
## Events
`hospitality.qr_code.created`, `qr_menu_session.created`, `qr_ordering_session.created|submitted`, `cart.created`, `cart_line.added`
## Migration
`0003_phase_122_qr_menu_ordering` (additive)
## Known Limitations
- No kitchen routing from submitted sessions
- No payment / Accounting journals
- Public unauthenticated guest auth via token only (tenant still required)
## Next Phase Entry
Phase **12.3 — Table Service & Reservations**
## Service Snapshot
Regenerated: `docs/service-snapshots/hospitality.yaml`