Source: third full-project audit (2026-07-25). Severity: HIGH. Category: half-fix regression (docs/current/VERSION_PLAN.md:79 named "README/ROADMAP/STATUS body lines outside the header" as a sibling path).
Evidence
docs/status/STATUS.md:14 — "Alpha.17 is the current published and verified line" vs :5 header v0.41.0-alpha.18 and :44 gates row "Alpha.18 npm, tag, prerelease and final evidence | Completed".docs/status/STATUS.md:59 — Release direction table still marks 0.41.0-alpha.17 as "Current verified published baseline", contradicting docs/roadmap/ROADMAP.md:116.- Closure commit
f15657fa only flipped the gates table; body prose untouched (git show f15657fa -- docs/status/STATUS.md).
tools/check-version-anchors.ts:123-130 scans only the header anchor zone; a read-only injection of an explicit stale body claim produced zero failures from both check-version-anchors and check-strategic-docs (verified via deno eval against the real files).- Same class:
STATUS.md:72 links only the alpha.17 record; ROADMAP.md:10-11,122 and README.md:57-59 present-tense staleness; SECURITY.md:12 "supported while alpha.7 is active".
Impact
The governance source of truth contradicts itself about the current release line; the drift regenerates every release bump because bump tooling maintains only header anchors.
Suggested fix
Reword to the alpha.18 reality (or de-version the sentences); extend the anchor/strategic gates with a "current ... baseline/published line" heuristic co-occurring with outdated versions, or convert those body lines into bump-maintained anchors.
Source: third full-project audit (2026-07-25). Severity: HIGH. Category: half-fix regression (
docs/current/VERSION_PLAN.md:79named "README/ROADMAP/STATUS body lines outside the header" as a sibling path).Evidence
docs/status/STATUS.md:14— "Alpha.17 is the current published and verified line" vs:5headerv0.41.0-alpha.18and:44gates row "Alpha.18 npm, tag, prerelease and final evidence | Completed".docs/status/STATUS.md:59— Release direction table still marks0.41.0-alpha.17as "Current verified published baseline", contradictingdocs/roadmap/ROADMAP.md:116.f15657faonly flipped the gates table; body prose untouched (git show f15657fa -- docs/status/STATUS.md).tools/check-version-anchors.ts:123-130scans only the header anchor zone; a read-only injection of an explicit stale body claim produced zero failures from bothcheck-version-anchorsandcheck-strategic-docs(verified viadeno evalagainst the real files).STATUS.md:72links only the alpha.17 record;ROADMAP.md:10-11,122andREADME.md:57-59present-tense staleness;SECURITY.md:12"supported while alpha.7 is active".Impact
The governance source of truth contradicts itself about the current release line; the drift regenerates every release bump because bump tooling maintains only header anchors.
Suggested fix
Reword to the alpha.18 reality (or de-version the sentences); extend the anchor/strategic gates with a "current ... baseline/published line" heuristic co-occurring with outdated versions, or convert those body lines into bump-maintained anchors.