docs/harness: close Phase 4, the wraptool:0 feature major is unsupported

pti commented

2026-10-20 08:57:04 +02:00

Owner

#107 item 3, stacked on #110 so merge that first and this diff shrinks to the two docs commits. Docs and design only plus two user-facing strings. The wraptool feature is 1.2.1 with a rewritten description matching current up behaviour, up requires the read-only runtime/ mount declaration and refuses with the exact entry, no more only verifies wording. The wraptool:0 major is documented unsupported rather than deprecated in CLAUDE.md, docs/devcontainers.qmd, docs/getting-started.qmd, docs/releases.qmd, docs/doctor.qmd, the doctor check text and the up attach hint, its published artifact stays. design/harness/unified-harness-pool.md section 16 Phase 4 is closed, design/release-1-0.md section 3.5 gets a completion paragraph and the section 1.3 and 4 bullets match current behaviour, the stale cursor gemini roo rows in documentation-onboarding.md and acp-bridge.md get notes. CHANGELOG gains one non-breaking bullet, the first Breaking bullet already tells users to run wraptool harness install name once after upgrading. TODO.md ticks the Before 1.0 retirement item but keeps one open sub-item, the reviewer found that up only notices and does not refuse an existing dev container lacking the runtime mount, filed as #111. Reviewer pass done, findings fixed in the second commit. Closes #107. Generated with Claude Code.

pti added 4 commits

2026-10-20 08:57:04 +02:00

feat(harness)!: stop creating or exposing the legacy bin/ and lib/ pool trees ad5be7931d

The pool generation is the only install since #102 and #107 item 1, so
nothing reads or executes from the pre-1.0 bin/+lib/ trees any more.
ensureHarnessPool now creates only home/ and runtime/, the guix runtime
exposes runtime/ read-only alone, and the mixed-state plumbing (legacy
state classification, guixPoolPlanInput, the legacy-removed marker) is
gone. gc --legacy stays as an explicit opt-in one-time cleanup of any
leftover trees, without the refusal check or the marker. harness list
ACTIVE only reports the activated generation's version, and the
PoolLockable guards (every registry harness is pool-lockable) are
dropped from cmd.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

fix(harness): gc --legacy also removes the stale pre-1.0 marker, tidy wording

Lint / lint (pull_request) Successful in 37s

Details

Lint / sonarqube (pull_request) Has been skipped

Details

f47fb63bc4

Review nits on the layout cleanup: a pool that ran the pre-1.0
`gc --legacy` keeps its `legacy-removed` marker file forever, with no
reader left; gcLegacy now removes it as part of the one-time cleanup.
Reflow over-long comment lines, drop the last "mixed state" /
"legacy-feature" / "not pool-lockable" wording from CLAUDE.md and the
design notes, and name the trees "pre-1.0" consistently in releases.qmd.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs(harness): close Phase 4, mark the wraptool:0 feature major unsupported 8422769045

The legacy install step and bin/+lib/ layout are gone (#102, #107), so
the per-image provisioning feature major is no longer merely deprecated.
Feature 1.2.1 rewrites the description to match current up behaviour
(the read-only runtime/ mount declaration is required, not just verified).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs(harness): review fixes for the Phase 4 closure, reopen the stale-container item

Lint / lint (pull_request) Successful in 37s

Details

Lint / sonarqube (pull_request) Has been skipped

Details

ad134febe7

The TODO entry had ticked a sub-item that is not done: `wraptool up` only
notices, and does not refuse, an existing dev container that lacks the
runtime mount, so a container built against `wraptool:0` keeps running
its per-image binary. Reopen it as a sub-item pointing at #111.

Say "unsupported" instead of "deprecated" for the `wraptool:0` major in
the doctor check text, the `up` attach hint and the related comments, so
the tool and the docs agree. Tidy the release-1-0.md notes (the §3.5
pre-#102 note sits under the heading, §1.3 and the §4 bullet match the
current gc --legacy behaviour), wrap the onboarding note and attribute
the registry change to cbcf187, rewrap one docs paragraph.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

pti referenced this pull request

2026-10-20 09:02:12 +02:00

fix/pool: report a stalled download as a stall even when the body ends cleanly #113

pti merged commit c21e553ddf into main

2026-10-20 09:20:47 +02:00

pti referenced this pull request from a commit

2026-10-20 09:20:49 +02:00

Merge pull request 'docs/harness: close Phase 4, the wraptool:0 feature major is unsupported' (#112) from feat/phase4-closure into main

Rows
Columns

docs/harness: close Phase 4, the wraptool:0 feature major is unsupported #112