Skip to content

v0.2.3 — H3R enforcement-point migration + fix round

Choose a tag to compare

@Acfufu Acfufu released this 22 Sep 16:50
· 468 commits to main since this release

Highlights

  • H3R enforcement-point migration (ADR-0022 amendment): the dormant
    high-risk-step prototype gains two machine faces in the unattended lane —
    one-step-per-segment (LZY_SEGMENT_ID, shape-validated <int>:seg-<int>,
    a second distinct step done in one segment is refused; same-step evidence
    rebinds pass) and a command-layer gate (plugin/hooks/h3r-pretool.js,
    PreToolUse/Bash, awake only with LZY_ABLATE_H3R_PRETOOL=1) that denies
    word-list hits and writes the hit marker drive consumes for a clean
    wind-down. Grid h3r2 (32 trials): decisive split — protected arms stop
    4/4 with zero high-risk actions landing (report includes a re-derivation
    errata: true deny events 4, true one-step refusals 11, echo amplification
    ~109x).
  • Fix round (five-round dual review, 41 findings all handled): drive's
    wind-down channel is non-throwing (every non-done cause authors its 7-field
    snapshot), heartbeat failures split by family (storage I/O no longer
    mislabeled as takeover; snapshot + lease-reclaim guidance), segment-boundary
    recovery guidance dispatches by cause (RESTRICTED's only exit is
    narrow-and-re-register), reset/start sweep the segment markers, the
    bookkeeping exemption refuses compound commands and quoted paths, the word
    list closes the push -f / id_ed25519 / whitespace-evasion gaps, and the
    word-list check now states its per-reader failure semantics (drive-side
    throws, hook-side fails open).

Coverage boundary

  • The H3R gate remains a dormant prototype for the unattended lane only
    (ADR-0022): default behavior stays byte-identical to 0.2.2, interactive
    sessions are exempt (given env hygiene) and are the recovery path. Its
    machine form's fate (wake default / removal) is deferred to human review —
    never auto-promoted or auto-dropped.
  • win32: the run-hook.cmd version-sort guard is verified by diff + cmd
    semantics argument; the VM live-shot is on this release arc's retest list.

Upgrade

  • From 0.2.2: lzy update — npm pulls the latest package, then a fresh child
    process from the new install runs lzy sync (skips when already latest).
  • From 0.2.1 or earlier: the manual two-step (see the guide's Upgrade
    section) — engine sessions read the cached version directory, so npm alone
    does not take effect for running setups.