feat/harness!: the pool stops creating or exposing the legacy bin/ and lib/ trees #110
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/pool-drop-legacy-layout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#107 item 2, after #108 and #109. The harness pool layout no longer creates or exposes the pre-1.0 bin/ and lib/ trees. ensureHarnessPool creates home/ and runtime/ only. The guix runtime exposes runtime/ read-only alone and the legacy-removed marker is gone, so there is no mixed state, no half-gone classification and no gating. harness gc --legacy is now a plain one-time removal of whatever is left of the two trees plus the stale marker, with no refusal check. harness list ACTIVE only reports the activated generation version, the legacy row is deleted. The dead PoolLockable guards, the sbx refusal, poolPlanInput.PoolLockable, harnessDeps.poolBinDir and the dead bare-shell branch of buildDevcontainerExecArgs are removed, every registry harness is pool-lockable since #109. Breaking: a pool from an older release keeps working, run wraptool harness gc --legacy once to drop the leftover trees. CLAUDE.md, CHANGELOG, docs/releases.qmd, docs/cli-reference.qmd and the design notes are updated. Phase 4 is not declared closed yet, item 3 does that with the feature description bump. Reviewer pass done, five nits fixed in the second commit. Refs #107. Generated with Claude Code.