Repository navigation
Description
Status
OPEN FOLLOW-UP. Hardening backlog disclosed by PR #92 itself (accepted head 52627c33f0c3b58e9ce68e0573fc67f0566d5c87, merged as f1ac458731e23da2c48ca3ef84f44992727f76fe). Source of record: PR #92 "Disclosed non-blocking residuals and claim corrections" and docs/q-deck/a0-candidate-state.md.
Rules
- This backlog does not reopen A0 acceptance. None of these items make the accepted A0 incomplete — every one was disclosed at acceptance time, classified, and carried deliberately.
- Each item carries its own severity and blocking boundary; fixes land as individual reviewed changes with severity-appropriate ceremony.
- A1 contract work proceeds in parallel — no item below changes A1 artifact semantics. If one turns out to, that discovery escalates to the A1 freeze discussion first.
- All deployment/replay-critical items must be adjudicated (fixed, or explicitly re-accepted with rationale) before A2 deployment / campaign-reducer freeze.
Carried availability/hardening items
| # | Item | Severity | Blocking boundary |
|---|---|---|---|
| 1 | o7::recovery::classify_command_child performs an unbounded, symlink-following read_to_string on the stale-command redrive path reachable from POST /commands |
availability | before A2 deployment |
| 2 | Aggregate hydration accounting charges the fstat size rather than final observed bytes if a regular file grows during reading (per-artifact cap remains enforced); the aggregate hard-bound claim should be tightened or the accounting fixed |
claim accuracy | before A2 |
| 3 | Missing explicit HTTP contract test binding saturation to 503 CANDIDATE_REPLAY_BUSY and proving zero durable mutations |
test coverage | before A2 |
| 4 | Stale private candidate temp-file cleanup deferred pending a safe lock/lease design | hygiene / disk | before A2 deployment |
Round-7 adjudications carried as documented residuals
Recorded classifications, unchanged by this issue (details: PR #92 body items 5–9):
- rejection-path index staging semantics ("exactly as found" was too broad;
git add -Aruns before the new check) — classified as existing dedicated-worktree staging semantics, not an authority defect; git apply --indexmay clear a hidden-index flag on a patched path — resulting tree independently proven byte-identical; no stale/false authority;- no explicit locking model against a concurrent external
git update-indexbetween checks and authority construction — documented hardening residual, no demonstrated exploit in the server-owned worktree model; diff_vs_baseshares the hidden-index blind spot — all three consumers traced; itsdiff.patchis evidence-only and gates neither A0 authority nor dispatch/admission;- pre-existing R1 crash-redrive fixture race — NOTE-level test-harness debt.
Round-8 audited-not-implemented (no independently reproduced defect)
Separate admission/projection semaphores; replay caching; helper-only test refactors; parent-directory fsync; porcelain-v2 u-record handling; dead continuation base fallback. Optional improvements — adopt only with a demonstrated case.
Non-goals
Not a place for new features, A1 semantics, or reclassifying A0. "Hardening" here means closing disclosed residuals of the accepted implementation, nothing wider.
Activity