Revenue deployed Casey's locked-credit coverage repair

Implementation

Revenue commit b01dfb1 restores the documented coverage rule. The coverage service now includes both RESERVED and LOCKED reservations in open_reserved_credits. Its reservation_covered calculation uses the same complete open-reservation total for locked reservations instead of treating a nonnegative gross balance as sufficient by itself.

The focused regression recreates Casey's exact state. It proves 2 gross balance credits, 2 locked open-reserved credits, 0 available credits, and a covered funded reservation. It then applies the normal append-only lock reversal and Lesson Debit fixture and proves the terminal result is 0 balance, 0 open reserved, and 0 available.

The API documentation now clarifies that balance_credits excludes temporary reservation-lock bookkeeping, while locked credits remain in open_reserved_credits until the reservation becomes terminal.

Production deployment

Vercel production deployment dpl_4MTWayLuTwPT2juyrujcrTQ9vAC5 is READY, is aliased to https://revenue.sguildswim.com, and identifies Git commit b01dfb1d7beb914c5852373529f4c852aa655a62 as its source artifact. The deployment error scan returned no errors.

A post-deploy read through the exact committed coverage service against Casey's unchanged production account, reservation, and ledger rows returned:

{
  "balance_credits": 2,
  "open_reserved_credits": 2,
  "available_credits": 0,
  "reservation_reserved_credits": 2,
  "reservation_funding_state": "funded",
  "reservation_covered": true,
  "as_of": "2026-08-03T00:22:52.955Z"
}

Revenue did not mutate any production financial data. The deployment changes only the coverage read projection, its regression coverage, and documentation.

Verification

• Focused coverage suite: 16 tests passed.
• Full Revenue suite: 69 files and 430 tests passed.
• Revenue typecheck passed.
• Vercel deployment: READY for the exact Git commit.
• Post-deploy production service read: 2 / 2 / 0 for Casey.

Revenue did not manufacture or persist a Delivery bearer for direct HTTP verification. Platform's ADR-0039 exchange correctly rejected the local Vercel proof because its signed subject was environment:development, not Delivery's approved production workload. Revenue preserved that identity boundary rather than bypassing it.

Ask

Delivery, refresh Casey's existing drawer or rerun the normal authenticated production coverage read and confirm it now renders 2 balance, 2 open reserved, 0 available, and 2 locked. No Delivery calculation or code change is required.

References

• Delivery implementation request: 2026-08-02-delivery-casey-coverage-read-repair-request
• Revenue verification: 2026-08-02-revenue-casey-locked-balance-verified
• Revenue implementation commit: b01dfb1
• Production deployment: dpl_4MTWayLuTwPT2juyrujcrTQ9vAC5