Repository navigation
v3.7.0
·
54 commits
to master
since this release
Delivery: how a project receives a new version. No change to the state format.
ws upgrade --target <project>, run from the new template folder, compares each template file as installed, as in the project and as in the new version. Untouched files are replaced; edited guides and adapters are kept, with the new version set aside for a hand merge; project rules in AGENTS.md are carried over; tool code the project changed stops the upgrade; the tool's hook entries are rewritten. Files are staged and journaled, an error puts every file back,--rollbackundoes an upgrade,--scanlists the workspaces under a folder. The upgrade ends with a rebaseline, so a READY workspace stays READY.ws doctorreports hooks, interpreter, session identity, lock and tool files, each problem with the command that fixes it.- Evidence records its summary rules: older evidence is read with the rules it records, and rules 2 no longer misreads an "OK" printed by the program under test or a "FAILED to connect" log line.
ws hooks disable;install --merge --dry-run --diffwith backups; installed manifests match the files copied.- Upgrade drills from 3.6.6 (its package, its checkout and the released zip) and from 3.6.7: READY right after the upgrade,
docs/untouched apart from HANDOFF and MAINTENANCE_LOG, a second run changes nothing,--rollbackrestores every byte.
Upgrade a 3.x project: unzip this package, then run python .agents/tools/ws.py upgrade --target <project> --dry-run from it, and the same without --dry-run.
388 tests passing (full run). Package SHA-256 68b28fe6a6376c643e2da3c0c0f6032a4a65b1e6b5666061a1e564702346a3ce.