Delivery local ADR-0046 schema is ready and verification stops at missing Platform Person
Delivery repair completed
Delivery reviewed its four pending migrations and applied them only to the validated local platform_local database at 127.0.0.1:55434, scoped to schema delivery. The applied migrations add guarded outcome correction state, guarded details correction state, reservation-lock audit state, and completion-charge adjustment state. The only existing-row update backfills terminal lesson outcome versions; no rows, schemas, fixtures, or production data were deleted or reset.
Prisma now reports all 42 Delivery migrations applied. delivery.lesson_outcome_correction, delivery.lesson_details_correction, delivery.reservation_lock_audit_run, and delivery.lesson_completion_charge_adjustment are present. Delivery's required tables, deterministic seed fixtures, dispatcher proof rows, service area, and shared fixture identifiers otherwise pass the local mesh readiness check.
No production migration, deployment, flag change, Square call, purchase, reservation, or financial mutation was performed.
Matching Delivery identity
Delivery's matching active participant is par_01900000-0000-7000-8000-000000000201. It references per_01900000-0000-7000-8000-000000000101 in Organization org_01900000-0000-7000-8000-000000000001, as expected by the shared fixture spine.
The existing deterministic lesson is not a usable proof candidate in its current state. It is canceled, its primary reservation lock is released, and the additional stale lock remains a negative-path fixture. Delivery will use the normal idempotent local seed or scheduling path after canonical identity is restored rather than rewriting these rows manually.
First remaining broken boundary
The verification now stops at canonical identity. platform.person does not contain per_01900000-0000-7000-8000-000000000101. Delivery tightened its local readiness check so --require-ready now fails explicitly at platform person fixture instead of reporting a misleading ready state.
Platform, please restore the canonical synthetic Person or publish a fresh synthetic Person id and the corresponding identity and service-auth setup. Preserve the current shared database and existing fixture graph. Once Platform confirms that boundary, Delivery will rerun the mesh seed and readiness check, verify scheduling and completion against the local mesh, and hand the clean lesson and participant ids back to Revenue for the Square sandbox proof.
Revenue, Delivery's schema prerequisite is cleared. Revenue should continue to hold sandbox purchase and correction apply until Platform identity passes and Delivery produces a clean scheduled lesson with an active funded reservation mirror.
References
memos/2026/2026-09-22-revenue-adr-0046-local-sandbox-preflight.mdmemos/2026/2026-09-22-delivery-adr-0046-controlled-proof-candidate-blocked.mdadrs/ADR-0046-guarded-lesson-completion-charge-adjustments.md- Delivery
scripts/check-local-mesh.mjs