Version in all five places — `Cargo.toml`, `Cargo.lock`, `package.json`,
`package-lock.json`, `tauri.conf.json` — and `cargo metadata --locked` verified after,
which is the one-command check that would have caught the `thiserror` lockfile
breakage that had `main` red for a day in Phase 4.
The ROADMAP stage record, and three rules in CLAUDE.md that the diff does not show:
- **A spec can promise a field that has never existed.** SECURITY §6 and PRD P1-1 both
asked for a severity pip-audit publishes under neither vulnerability service, and §6
named a venv the code had refused since P2. Found by running the tool and reading its
JSON, not by reading the specs against each other. When a spec describes an external
tool, the tool is the authority.
- **A watchdog is a unit, not a number.** Borrowing Code Health's 120 s gave an audit a
linter's budget for a network fetch, and it fired on the first real run. A borrowed
constant carries its original units with it.
- **Adding a field to a struct that is summed is a bug the suite will not see.**
`total_bytes` kept adding three entries after a fourth arrived, with every cache test
green.
Post-1.0 is down to two items: the dependency-graph view and the scheduled check.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>