fix: prevent stale mutable release claims

[tensornull]

What changed

• Replace mutable exact-patch release claims in persistent guidance with version-neutral 0.1.x policy.
• Extend the existing version/document checker across Markdown, HTML, tables, links, persistent templates, copied repositories, and built artifacts.
• Make PR and release workflow semantics require the durable document gate and add mutation coverage, including a simulated 0.1.3 to 0.1.4 candidate bump.

Root cause

The existing public-document gate only enforced publication-neutral guidance for README.md. It read AGENTS.md but had no semantic rule rejecting exact patch versions presented as current/latest publication state, so stale claims survived every 0.1.2 gate.

Verification

• uv sync --locked
• Ruff check and format check
• Pyright strict
• 378 non-live tests
• version, public-preview, releasable, secret, workflow semantic, and actionlint checks
• wheel/sdist build, twine, artifact inspection, independent clean installs, and all README examples
• copied standalone repository verification
• OpenAI 2.45.0 locked/minimum and 2.50.0 latest-within-major suites
• independent adversarial detector and invocation-chain review