ADR-0046 local sandbox proof needs mesh schema and identity repair

Operator direction and completed recovery

The operator authorized proceeding with local testing using Square sandbox, not creating production test charges. Revenue restarted the existing stopped Postgres 17 mesh cluster at 127.0.0.1:55434. Its existing data directory is C:/Users/jallr/AppData/Local/Sguild/postgres/local-dev-mesh/data. No database reset, seed, migration, purchase or financial mutation was performed. The unrelated Postgres service on port 5432 was left alone.

Read-only checks on platform_local confirm Revenue account crd_acct_01900000-0000-7000-8000-000000000101 exists. Revenue, Delivery and Platform local configuration all target separate schemas in this local database. Revenue's Square endpoint is connect.squareupsandbox.com. Credentials were not printed or changed.

First broken prerequisite

The existing local database is older than the deployed feature. Both revenue.lesson_outcome_corrections and delivery.lesson_completion_charge_adjustment are absent. Delivery has 93 local lessons, but the documented shared Person per_01900000-0000-7000-8000-000000000101 is absent from platform.person. Existence of the Revenue fixture alone does not establish an eligible cross-domain test customer.

Revenue prisma migrate status identifies nine pending migrations. A blanket deploy is not safe for the intended preserved fixture: migration 20260802213000_quarantine_production_fixture_spine unconditionally selects the shared fixture Person or market, changes the account to Quarantined Fixture, and enables a trigger rejecting those identifiers. Other pending migrations include production-specific data repairs. Revenue did not run that batch, skip migration history, disable guardrails, or use db push --accept-data-loss.

Requests and next boundary

Platform, please restore or identify a canonical synthetic local Person and confirm the existing local identity/auth and service-routing setup without resetting shared data. Delivery, please review and apply its non-destructive local feature migrations through its owned workflow, identify the matching test participant, and confirm local scheduling and completion can run entirely against the mesh. Do not edit production or enable the production flag for this repair.

Revenue's next prerequisite is a reviewed non-destructive local schema upgrade that accounts for the production-specific migrations above, before any sandbox purchase. An isolated new test graph with fresh canonical IDs may be preferable to reusing the old deterministic fixture; that decision must preserve the existing data and keep production quarantine protections intact.

After these prerequisites are repaired, the intended proof is normal Square sandbox purchase, funded reservation, Delivery scheduling, six-to-three completion preview/apply, replay and finalization recovery, with ledger and source recognition evidence. No full-flow success is claimed. Please also explicitly confirm the remaining production release checks if sandbox proof is to replace the previously requested production financial mutation. The production UI flag remains disabled.

References

• memos/2026/2026-09-22-delivery-adr-0046-controlled-proof-candidate-blocked.md
• Revenue docs/local-dev-mesh.md
• Platform docs/local-dev-mesh.md
• adrs/ADR-0046-guarded-lesson-completion-charge-adjustments.md