Repository navigation
v0.4.0 — policy engineering: review runner, findings, scope reuse, migration apply
Highlights
0.4.0 is the policy-engineering release: the discipline layer learns to prove itself.
- Controlled independent review runner (
lzy review run|list|show): real isolated review sessions against your goal — facts-only input package, candidate snapshot, isolated HOME, sealed raw output, per-session subledger metering. Exit-code contract 0/1/2/3. - Finding lifecycle (
.lazyzcode/findings/, loop-external): blocking findings land in a checksummed ledger, block the unified gate until closed through the single channel —resolve-request → review recheck → finding close. Two invalid fix cycles demand a root-cause diagnosis. Renamed goals stay chained (finding relink). - Obligation reassessment (
lzy policy reassess): an extra obligation whose generating condition disappeared can be cancelled with a three-part independent rationale — baseline and tier-floor obligations are refused. - Review scope qualification & reuse: declare a review's scope, get adversarially challenged across ten axes, and let an untouched candidate reuse the earlier review (
review qualify/review reuse). Closure bases are audited for applicability;finding reopenis the controlled re-entry. - Migration apply end-to-end (
lzy migrate apply): backup → stage → verify → atomic switch with a phase journal — a kill at any phase resumes idempotently;STATE_VERSION 0.4.0, older states stay readable. - Paired evaluation harness (
scripts/evaluation/run-pairs.mjs): sealed tasks × baseline/candidate arms × 3 trials with interruption+resume legs and an independent sealed oracle — the 0.4.0 batch report is at docs/reviews/v040-policy-evaluation.md (honest reading: quality gate not met; adoption deferred to 0.5.0 re-evaluation, decision #42 / ADR-0034). - Docs link checker + CI docs job, structural-axis real drift injection, gate reuse env axis, fixture materialization containment + symlink-faithful copies.
Coverage boundary
Live evidence covers arm64 (macOS host, Parallels Windows 11 aarch64 VM per prior releases; CI matrix ubuntu/windows × node 22/24 for the test suite). The paired evaluation ran three real repositories (lazyzcode / openchamber / zpigeon-ios) on darwin; oracle check-2 of the lazyzcode leg carries a disclosed Node ≥22 glob-semantics limitation (threat boundary in the report). sqlite3 remains an optional dependency: metering reads degrade to absent with named notes, and review preflight refuses cleanly when absent.
Upgrade
From 0.3.x: lzy update (or npm i -g lazyzcode@0.4.0). Requires the ZCode desktop app (logged in), Node ≥ 22, git. In-flight v1 goals keep running under legacy rules with a version stamp; explicit lzy migrate apply moves them into the v2 format (in-flight goals become drafts with authorization NONE — re-adopting needs a fresh human approval; update/sync never migrate automatically).