Record and explain task attempts consistently #56
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#56
Reference in new issue
Block a user
Production Task 1 shows current attempt 3 missing while recorded attempts 1 and 2 have unknown outcomes. Reproduce early preparation failure and retry accounting through the State Store and task page; correct the producer or projection responsible rather than hiding inconsistent data. Include actionable recovery from clone failures and verify the existing failing-log navigation issue.
Acceptance criteria
A failure before workflow execution and successive retries each have truthful attempt state, outcome and failure reason. The current attempt is never presented as a phantom completed run. Unknown historic state is labelled honestly. A failing-log link reaches the line or explicitly explains why none was recorded.
Notes
Early parks now publish attempt-attributed events through the shared daemon park path. The API includes claimed attempts and step-only attempts, uses explicit park/retry evidence for historic failures, and preserves unknown outcomes where evidence is absent. Current failure reasons are visible before any stage starts. Unit regressions and the live local task/log-focus check pass. Existing log-navigation issue archie-core-4pv3 is verified by the browser check; credential recovery navigation remains owned by archie-core-oygqd.
Close reason
Implemented and verified in
57456b3e. Full quality gate passed, seven targeted local browser checks passed, and real audit-name save/readback was verified with the original setting restored. Per-issue acceptance evidence is recorded in notes.Imported from beads
archie-core-3z4fd.7· GitHub #1686 · type task · priority P1 · created 2026-10-16 · closed 2026-10-16