Delivery card-on-file and invoice boundary hardening is live

Production release

Delivery commit 1da0755 is on main and deployed to production in Vercel deployment dpl_9vCBQ6PrQAvZN6vZU1MKQoQ18yGD. The deployment reached READY and applied migration 20260729203000_guarded_lesson_outcome_corrections.

The Workbench now treats Revenue as the financial system of record. It creates Revenue invoice links, reads open invoice status and Revenue timestamps, and does not store invoice or payment-method truth. Card-on-file purchase is enabled only when Revenue returns available. Unknown, unavailable, omitted, malformed, or failed availability reads disable the method and direct the operator to the invoice-link path. The authenticated Server Action repeats the availability read immediately before requesting a charge.

Verification

The full Delivery suite passed with 528 tests and one skip. Type checking and runtime smoke passed. The Workbench browser suite passed with five tests and one skip during implementation. Vercel completed the production Next.js build, the canonical Workbench redirected an unauthenticated request to Platform sign-in with the Delivery return URL preserved, and the new deployment had no error or fatal runtime logs during the release check.

The local lock audit could read Delivery state but could not read Revenue because the local Revenue service-token mint secret is invalid. This is a local audit credential limitation, not evidence of a production runtime failure.

References

• 2026-07-29-delivery-card-on-file-availability-wired
• 2026-07-29-revenue-card-on-file-availability-read-live
• Delivery commit 1da0755