Skip to content

fix(recovery): report actionable lifecycle blockers - #274

Merged
ebarti merged 9 commits into
mainfrom
fix/recovery-lifecycle-240
Nov 1, 2026
Merged

ebarti merged 9 commits into
mainfrom
fix/recovery-lifecycle-240

Conversation

@ebarti

@ebarti ebarti commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

Stopped deliveries can retain an unchanged candidate while cleanup, ownership, effects or a repair allowance still prevent continuation. Selected recovery routes now expose versioned lifecycle observations and typed blockers from the same owner checks used by admission. Historical repair rechecks its frozen run, claim, work/repository binding, attempts and effects inside the admission transaction.

Exact command replay validates the required receipt fields and workflow identity against retained grants, admissions and events. Corrupt or conflicting receipts fail closed; later workflow progress does not invalidate an authentic earlier receipt. Historical repair and stopped-resume records cannot independently reconstruct every presentation field, so those limits remain explicit.

This is a bounded contribution to #240. Pre-plan same-run recovery, typed refusals for every owner and replacement of existing error-text classification remain open. The gate guard overlaps #276 and requires reviewed integration before joint delivery. Native descendant settlement and full issue acceptance are not established here.

Validation on 8121ac2981c00fd20636300126562bd7feb1add3:

  • 32 affected local cases passed, including public API, Git/SQLite, local Temporal, concurrent identical admissions and replay after later admissions.
  • Runtime Ruff and diff checks passed.
  • Hosted Check 41332643263 and current CodeQL passed on the exact head/base. Five jobs, both ZIP digests, and four complete disjoint reports/JUnit were authenticated: 1,426 runtime passes and 188 source passes. Four existing runtime and three existing source opt-in/capability skips remain unexecuted. This is configured hosted-gate qualification, not production or full issue acceptance.

@ebarti
ebarti added this pull request to stack #277 November 1, 2026 18:03
@ebarti
ebarti merged commit 2d52d3f into main Nov 1, 2026
9 checks passed
@ebarti
ebarti deleted the fix/recovery-lifecycle-240 branch November 1, 2026 19:31
ebarti added a commit that referenced this pull request Nov 1, 2026
A transient prelaunch stop can abandon a retained passing implementation
and schedule product repair. Authenticate candidate-bound readiness
refusals and add a finite zero-repair continuation that preserves the
original attempt, selectors, owner, effects and product allowance. Two
readiness retries use 30- and 60-second backoff from authenticated
predecessor closure; waiting creates no attempt, effect or grant.

Early feature-review preparation failures are distinguished from genuine
findings through sealed revision/proposal identity, typed terminal
supervisor evidence and held owner/resource leases. This integration
consumes #274 while preserving its typed predicates and every readiness,
worker-handoff and custody check.

This is a bounded contribution to #243. Native retry remains refused
without complete descendant settlement. Feature reservation/GO
reconciliation, other infrastructure routes, generic early-prelaunch
observation and full public product-repair acceptance remain open.

Validation of unchanged integration tree
`849152544b063227aa4fb76cd6dc437d30c18e37` (current head
`200a4d80dd3614dab27c00a63655ab5c7d41c900`), based on #274:

- 21 existing public readiness, worker-handoff, gate and lifecycle cases
passed in 27.99 seconds, including local Temporal and controlled-clock
zero-debit checks; no skips.
- Runtime Ruff, per-layer diffs, signature verification and independent
reconstruction of the integrated tree passed.
- Fresh hosted Check run 41338611024 is under qualification for this
final head/base; earlier successes do not qualify it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant