build(docs): automate scoped current-version updates without rewriting release history #168

Verified maintenance cost

At main 90481b148584926ea328ed956327f3050d9be9cb, a literal source scan found 131 occurrences of 0.5.1 across 14 tracked Markdown files. This count includes dated evidence and intentional compatibility rows; it is not a claim that all occurrences should be replaced.

• package.json version and protocol.ts version are separate literals.
• Repository checker already verifies package/lock/runtime consistency, and README/guide checks require versioned examples.
• README examples and guide version context repeat the current release across four languages.
• The current PARITY summary still says source VERSION=0.5.0 beneath the 0.5.1 patch section. docs(parity): add a current scoped feature matrix and decisions for newer Python workflows #167 tracks the content correction; this issue tracks preventing repeat manual drift.

Proposed bounded improvement

Use an explicit current-release source/template or a safe scoped update command for the runtime constant and current examples. Preserve authored translations, exact historical versions, release evidence, source hashes, finite compatibility matrices and independently versioned skill/native/Python pins.

Acceptance criteria

• Inventory current-version fields versus intentional historical or compatibility literals; document which fields are generated or updated.
• Provide deterministic generation or a check/update command sourced from package metadata. A global search-and-replace is not acceptable.
• Retain a non-mutating CI drift check and existing package/lock/runtime, four-language, local-link and anchor checks.
• Add regression fixtures proving idempotence and a synthetic patch-version update, with historical records and independent pins unchanged.
• Verify build/package smoke and documentation checks against a synthetic next version before adopting the workflow; record checks actually run.

Related scope and limits

No release, dependency, compatibility-policy, publication or runtime behavior change is requested. #33/#35/#117 cover historical document content and release-record correctness, not an automated version-maintenance mechanism. All current issues and PRs were reviewed for duplication. The count above was computed from fetched pinned source; no TS tests, npm pack or build was executed during this audit.