Repository navigation
v0.0.10 — the review-fix train: all 44 findings closed
Highlights
- 0.0.9 five-round dual review closed out: all 44 findings fixed — P0×1, P1×4, P2×18 plus all 21 P3s swept opportunistically, each P0/P1/P2 with live red-green evidence (red half captured on published 0.0.9). 224/224 tests green (baseline 211).
- Ledger safety (P0): an unreadable
dag.json(permissions/directory) can no longer be silently treated as an empty ledger and overwritten — checksum-legal but malformed ledgers now fail closed with recovery pointers too. - Comparator attestations bind evidence: verdicts must anchor to the captured green half (node id + generation); compare-before-evidence, reuse-after-rebind, and cross-reset reuse are dead ends now.
- Three deadlock families got real exits (zero-F HEAVY, done-state divergence, legacy no-planHash goals) — machine gates stay fail-closed, doctrine recorded in the ADR-0014 addendum.
- Instance isolation across resets: pairing/supersedes/anchoring are scoped per attempt; the manifest view shows the current anchored green and stops mixing instances.
- Finish hardening: half the git rounds in the critical section, post-gate race recheck, same-second attestation suffix — no self-contradictory LOOP_COMPLETE.
- doctor payload-ver deep checks: registry pin, content-level sample, all marketplaces; plus a payload-freeze rule in the release checklist (nothing packaged changes after tagging).
- Per-provider rate-limit advice (debt 6): provider bands carry cap advice; a mix-note states how many providers the account-level numbers blend. Additive lines only.
Coverage boundary
Fix release only — no new features. The SOTA V3 two-tier protocol work (attempt lineage, invalidation propagation) and the headless driver face are the 0.1.0 train (next release). Full adjudication table: docs/reviews/2026-09-17-v009-five-round-dual-review.md.
Upgrade: lzy update (0.0.7+) or the manual two-step npm install -g lazyzcode@latest && lzy sync.