Skip to content

0.6.0 — SQLite switch release

Choose a tag to compare

@Acfufu Acfufu released this 23 Oct 19:18
· 60 commits to main since this release

The SQLite switch release. Goal-loop queue/budget/ledger state moves from loose JSON files to a single state.sqlite (node:sqlite, zero new dependencies) behind an explicit, one-way migration — plus the P4 review fixes and real-platform validation that gate the switch.

Highlights

  • lzy migrate sqlite <root> — explicit JSON→SQLite migration (backup → import → reconcile → atomic install → backend-marker commit; idempotent resume; never overwrites an existing DB).
  • Single-authority read gate — once migrated, the DB is authoritative; missing-DB and unrecognized-marker shapes get named diagnostics instead of silent JSON fallback.
  • Legacy-JSON miswrite detection — post-freeze writes (including the frozen=null family) are refused with a delete-and-retry self-heal path.
  • lzy doctor sqlite-store row — five-state observability; new workspaces still start on JSON (migration is always explicit).
  • Runtime floor: Node ≥ 24.0.0 — enforced by engines >=24; the Node 22 line is out of the support surface.
  • P4 fixes — migration micro-window kill re-entry re-anchoring, hook marker-shape gate alignment, doctor attribution split, probe script PATH/pipefail seams, TZ pinning in tests.

Coverage boundary

  • macOS host real-CLI battery: 29/29 (dispatch kill recovery, concurrency, migration interrupts/drift/corruption, hook paths, budget retention, backup-replay, engine 0.17.0 surface).
  • Windows 11 aarch64 VM: 10/10 (Node 22→24 in-place, NTFS migration chain, WAL converge + integrity ok, hook stdin legs, doctor).
  • Known warts recorded, not fixed: backup-replay same-dir rerun fails at VACUUM INTO (guard only checks state.sqlite).

Upgrade

npm i -g lazyzcode@0.6.0
lzy --version   # 0.6.0(插件载荷同版本)

Requires Node ≥ 24. Existing workspaces keep working unchanged; run lzy migrate sqlite <workspace> to switch a workspace to the SQLite store.