Highlights
- New prose-staleness checks (#334) in
docs-staleness-check.shPhase 7 — release-date consistency and count-prose scoped to 4 structured line shapes, closing a blind spot where stale counts (e.g. CLAUDE.md's "8 agent definitions") read GREEN for multiple releases. - Hardened the same day (#335) after a high-effort review found 9 defects, 2 HIGH, in #334's initial ship:
- Release-date check redesigned from a single git-tag authority (unreachable in CI, nonexistent at release time) to cross-file consistency — every claim compared against every other claim, majority wins. Promoted to
erroronce a clean live-repo run confirmed it. - Count-prose matcher boundary handling fixed for hyphenated compounds (
command-line) and markdown-bold badges (**48 commands**) — both previously misread or evaded detection. [e]xcludefixed for every Phase 7/9 finding (was a silent no-op).
- Release-date check redesigned from a single git-tag authority (unreachable in CI, nonexistent at release time) to cross-file consistency — every claim compared against every other claim, majority wins. Promoted to
- Teaching Mode feature removed — dead since the v4 command-prune split craft's teaching surface out to the
scholarplugin.
Test evidence
- Full suite: 2491 passed / 19 failed (all 19 pre-existing/environmental — installed branch-guard hook symlinks to the sibling
cc-configrepo, out of scope per cross-repo boundary; documented in v4.5.0's release notes too) pre-release-check.sh 4.6.0: PASSED, 10/10 checksdocs-staleness-check.sh: GREEN- Live-fire D11 promotion evidence: injecting a mismatched date into
docs/REFCARD.mdproduced"release date '2020-01-01' for v4.5.0 disagrees with other claims (majority: 2026-08-07)", reverted after confirming
Full Changelog: v4.5.0...v4.6.0