Unify commercial runtime ownership across backend and frontend so platform, experience, and hospitality modules use the shared commercial source of truth. Co-authored-by: Cursor <cursoragent@cursor.com>
36 lines
1.2 KiB
Markdown
36 lines
1.2 KiB
Markdown
# Phase Handover — Commercial Runtime Adoption
|
|
|
|
**Workstream:** Commercial Runtime Adoption
|
|
**Phase ID:** `commercial-runtime-adoption`
|
|
**Date:** 2026-07-28
|
|
**Status:** Complete
|
|
**Architecture status:** **COMMERCIAL_RUNTIME_ADOPTED**
|
|
**Readiness score:** **92 / 100**
|
|
|
|
## Objective
|
|
|
|
Migrate the platform onto Commercial Runtime SoT. Remove duplicated commercial catalogs. Do not rebuild the runtime.
|
|
|
|
## Delivered
|
|
|
|
- FE legacy catalogs deleted; billing/workspace/admin/tenant on commercial APIs
|
|
- Admin hub discovers from `/api/v1/commercial/catalog`
|
|
- Core onboarding + tenant context use commercial subscriptions
|
|
- Payment entitlement client calls commercial entitlements
|
|
- Legacy Core plans API deprecated
|
|
- Reports: adoption + legacy removal
|
|
|
|
## Remaining (documented, non-blocking)
|
|
|
|
- Delete legacy Core plan/feature tables in a later cleanup migration
|
|
- Soft L2 alias maps (hospitality / communication roadmap)
|
|
|
|
## Next
|
|
|
|
Follow `project-status.yaml` critical path (Payment 14.6+, Hospitality 12.9+, …).
|
|
Future products = registry rows only.
|
|
|
|
## STOP
|
|
|
|
No Marketplace / QR / Booking / Payment 14.6+ / Commercial Runtime rebuild.
|