Repository navigation
L05-06 — Qualify restartable batch publication #46
Description
Outcome
Demonstrate idempotent resume, atomic output, per-job provenance, and failure recovery across large batches.
Parent and boundary
Parent: #6. Owner: PdfTool. This issue owns one bounded slice of Production Orchestrator; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.
Acceptance
- Restart never duplicates publication or misattributes output; terminal failures remain inspectable.
- Failure case: Interrupted writes cannot leave a plausible success artifact.
Required proof
Kill/restart batch suite with exact output hashes and resource metrics. 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.
Activity
mberrys commentedon Oct 7, 2026
Related open question from
docs/adr/adr-004-pagemaster-batch-manifest.md:63: a process killed between the producer write andQSaveFile::commit()leaves<finalPath>.XXXXXXstaging residue (measured as 0-byte files). The ADR says the residue never lands at a final path but leaves open what cleans it up. The kill/restart suite here seems the natural place to decide and prove that, e.g. resume sweeps residue for outputs it owns, or the residue is documented as inert.