Install examples can no longer point at an old release
The docs told readers to install 0.2.6 while 0.2.7 was out. Fixed, and the project's own map now checks every install example against the package version.
A documentation bug, and the guard that keeps it from coming back.
The README, docs/agents.md and docs/enforcing-across-repos.md named 0.2.6 in their install, clone and CI examples while the package was already 0.2.7. Anyone who copied a command got the previous release.
They now name the current release. More importantly, Crossweft's own seam map now compares each of those install, clone, CI and pre-commit examples, the README status line and the Codex plugin manifest with the package version. If a future release forgets one of them, Crossweft's check on itself fails before the release goes out.
It is the same idea Crossweft applies to your code: a value copied by hand into several places is a seam, and a seam needs a guard.
Source: v0.2.8 · CHANGELOG.md