L12-04 — Recover idempotently after crash #89

Outcome

Persist run phase and exact identities so restart can resume or terminalize without duplicate publication.

Parent and boundary

Parent: #13. Owner: proposed Automation module. This issue owns one bounded slice of Automation Runtime; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• At every injected crash point, output count and provenance remain correct.
• Failure case: Uncertain publication state cannot be guessed successful.

Required proof

Crash matrix around plan, approval, publish, validate, and status transitions. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap.