Skip to content

v0.2.4 — dual-review fix round, honest gates

Choose a tag to compare

@Acfufu Acfufu released this 23 Sep 15:13
· 427 commits to main since this release

Highlights

  • 0.2.4 fix round — 39 findings of the five-round dual review, all closed
    (report: docs/reviews/2026-09-23-v024-fix-round.md). Every finding carries a
    landed commit in docs/reviews/findings-ledger.jsonl. The five P1s live in
    one family, the workers lane's wind-down phase:
    • the cleanup phase unlinks its worker-subject entries before deleting their
      worktrees (a clean non-done wind-down no longer leaves dangling roots that
      make every later finish reject), runs inside the lease window (a
      fenced subject remove is refused once the lease is released), preserves
      dirty worker worktrees with their branches, names them in the handoff
      snapshot, and only removes the run directory wholesale when nothing was
      preserved;
    • startup reclaim now deletes a run directory only when it carries the
      owner sentinel
      the tool writes at creation; foreign directories, .logs
      archives and sentinel-less ones are skipped and named (previously every
      non-current entry under the sibling root was rm -rf'd — including a
      maintained merge-conflict worktree);
    • the wave barrier re-anchors only when the subject head-tree set actually
      moved
      and passes the previous green's --harness through, so the stuck
      wind-down is reachable again and INV-08's harness freeze stops being
      vacuous on every rebind.
  • Workers-lane boundaries (ADR-0026): HEAVY goals are refused at the
    workers entry (structural dead end: every wave re-binds the anchored green,
    while HEAVY finish requires a comparator attestation bound to it), stranded
    per-run step claims are released at wave end with the snapshot naming the
    command, wall-clock accounting moved after the merge so a budget-exhausted
    wind-down keeps the wave's output, and the worker prompt forbids
    lzy loop finish with a pre-merge goal re-check.
  • H3R parser: four lexical gaps closed (segment truncation, bookkeeping
    prefix + newline, quote-parity misfire, mid-word quotes) — the real hook went
    from 0/4 to 4/4 on the four control cases. The bypass axes are now split into
    a fixed lexical family and a semantic family still reserved for lane B.
  • Read faces now say what the machines do: lzy evidence list warns only
    about the current red (matching the gate since 125bbdd), the doctor
    attest-trailer row distinguishes tampered content from absent files and
    never degrades an unreadable directory to "empty", and the doctor drive row
    reports workers residue in three buckets. --fast=false means the
    single-worker path (it used to be inverted into workers 2).

Coverage boundary

  • --workers N / --fast remains a LIGHT-only experimental lane for the
    unattended drive path: HEAVY is rejected at entry, measured request cost is
    ≈2× turns, and the barrier rebind is a fingerprint rebind, not
    re-verification
    (the evidence text says so). Idle/scheduled lanes are
    unchanged; the protocol (skills) carries the discipline, and the machine
    gates now enforce exactly what they claim.
  • The H3R gate remains dormant (L0 protocol text plus dormant prototypes); the
    word list is a matcher, not a command parser.

Verification

  • npm test 491/491 on the frozen tree (baseline 470; +21 new contract
    cases across the wind-down family, the reclaim matrix, the parser controls,
    the read faces and the ledger lint).
  • Real-surface evidence for this release: the workers probe (real CLI with a
    fake engine) went 1/13 → 13/13 pre-fix → post-fix; the real H3R hook 0/4 →
    4/4; the pre-change red captures and the post-change green captures are kept
    under artifacts/v024-fix-round/. Comparator attestation 6/6 MATCH;
    LOOP_COMPLETE at .lazyzcode/attestations/v024-fix-round-20260923T145524Z.json.
  • CI: node 22/24 × ubuntu/windows all green (run 35879379612). The first two CI
    attempts reddened on the new tests' environment assumptions (an ambient
    provider-config env that only a desktop session has; chmod 000 not blocking
    directory reads on Windows) — both fixed test-only, with the host env
    stripped locally to reproduce CI (491/491).
  • Payload: 44 files / 295.1 kB / sha1
    0ce271b9854acfba886434d99a1266ca5d4fd15e — the dry-run figure and the
    tarball packed from the tag tree are byte-identical (freeze held across the
    two test-only follow-up commits).