atomic-save-synthesis-canary

Metadata

Description

Implement the `atomic-save-synthesis-canary` work item from `docs/plans/atomic-graph-work-save-dag.json` and `docs/design-atomic-graph-work-save.md`.
This is the final synthesis gate. Integrate the exact outputs of every prerequisite, resolve only integration seams, validate an immutable candidate, and do not weaken fail-closed behavior to obtain a green canary.

Owned files/modules:
- `src/cli.rs`
- `src/main.rs`
- `src/commands/mod.rs`
- `docs/ops/runbook.md`
- `docs/design-atomic-graph-work-save.md (implementation conformance notes only)`

Non-goals:
- No weakening of fail-closed guards to make the canary pass.
- No automatic legacy blessing or cleanup.
- No provider, XDG sandbox, or broad TUI expansion.

## Validation
- `python3 -m json.tool docs/plans/atomic-graph-work-save-dag.json >/dev/null`
- `cargo fmt --check`
- `cargo check`
- `cargo clippy`
- `cargo test`
- `(cd formal && lake build)`
- `cargo test --test lifecycle_protocol_conformance --test save_transaction_conformance`
- `cargo test --test atomic_save_faults`
- `bash tests/smoke/scenarios/atomic_save_false_done_dependency.sh`
- `bash tests/smoke/scenarios/atomic_save_broker_handoff.sh`
- `bash tests/smoke/scenarios/atomic_save_crash_replay.sh`
- `bash tests/smoke/scenarios/atomic_save_dead_worker.sh`
- `bash tests/smoke/scenarios/atomic_save_reset_migration.sh`

Depends on

• done atomic-save-worksave-capture
• done atomic-save-terminal-adapters
• done atomic-save-daemon-convergence
• failed atomic-save-dependency-archive-reset
• done atomic-save-legacy-migration
• done atomic-save-formal-rust-traces
• failed atomic-save-adversarial-smokes
• done .assign-atomic-save-synthesis-canary
• done fix-nonsemantic-failed-dependency-convergence
• failed fix-stale-worktree-spawn-owner-convergence

Required by

• (none)

Log

• 2026-08-03T14:55:05.751301446+00:00 Task paused
• 2026-08-03T14:55:21.589539186+00:00 Task published
• 2026-08-03T14:56:58.332102758+00:00 Lightweight assignment: agent=Careful Programmer (02e87968), exec_mode=full, context_scope=graph, reason=A careful programmer best fits a correctness-critical final integration gate spanning multiple dependent components and requiring strict fail-closed validation.
• 2026-08-04T06:47:09.108709421+00:00 Remaining live integration checklist before canary: (1) promote retained-worktree capability/source-binding fix 7bb65c81 so current agent IDs can finalize against preserved source worktrees; (2) land dependency/archive/reset candidate (branch agent-981, commits through e94ec840 plus current HEAD) after that binding fix; (3) land adversarial suite 86d2c660; (4) extend ArchivedBoundary with GraphSave CID/digest before archived Done can satisfy dependencies; (5) update the two unowned raw-Done fixtures in src/commands/blocked.rs; (6) prove reset/retry consume the now-landed WorkSave prepared-base/intent/discard evidence; (7) add backward-compatible migration for worker-capabilities.json records missing save_source—the live rollout required preserving/removing the legacy registry manually; (8) ensure route-breaker/probe deadlines count as explicit scheduled convergence so the exhaustiveness monitor cannot pause the daemon; wrapper/finalization failures must not be charged as provider failures; (9) bounded evaluator evidence assembly is still infrastructure-unavailable and must remain non-semantic, while required deep FLIP and candidate smoke remain gating.