I read this as a focused implementation and offline authorization-publication task - I’ll inspect the repository and existing terminal/card workflow, apply only the schema/test changes, verify offline, then publish the requested one-use card if the local mechanism supports it.


I read this as implementation - complete offline resealing and publish exactly one fresh Owner one-use card without generation.


I read this as implementation - completed the offline schema repair, resealing, and one-card publication.

- Coach V2 strict schema now uses typed singleton enums; schema SHA-256: `28a712...3407b`.
- Published and verified one Owner DM card: message `146`, card `628e91...6638`, bound to sole prospective child `350b93eb6dae05af`.
- Journal is `published` with integrity verified; child append, provider generation, and customer delivery remain `0`.
- Restarted gateway to load the callback route; it is active and relevant ledgers stayed unchanged.
- Verification: 34 focused tests passed; Ruff passed. `ty` remains non-clean with 340 broader workspace diagnostics.