[rafiki270]

A saved DeepWater run needs a new Ledger attempt after a proven infrastructure failure. This adds POST /billing/v1/ledger/job-compute-renewals/:grantId/continue so Ledger can derive one compute grant for the same Water run, preserving the original identity, team, credential epoch, invocation and absolute expiry.

Continuation requires the original product-bound Ledger runtime key and a fresh delegation renewed from the exact parent grant. Current UOA authority and the full grant ancestry are checked under locks. The database enforces one child and immutable authority; generic chaining and fresh issuance reject job-bound tokens. The integration API documentation and deployment order are included.

Validation

• 21 PostgreSQL integration tests passed, including concurrent replay, ancestor revocation, credential revocation and a reproduced domain-disable race.
• Eight generic delegation unit tests passed.
• Root lint, typecheck and build passed on Maxis.
• A real local HTTP canary passed issuance, renewal, continuation, exact replay, conflicting replay and ancestor revocation.
• The broad API unit run initially had six missing Auth build-artifact failures; after the full build, both affected files passed all eight tests.

The Ledger and Water callers are subsequent changes. Production recovery and the original run's full report remain unverified at this prerequisite stage. No visible UI changed.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.