docs(release): reconcile v1.3.2 publication status in README and release records #351

Current state

At main f5e7c49554ff02771990a151e00b52f2abf3df0a, the README install section and Korean/Japanese/Simplified Chinese editions retain a dated preparation snapshot: source 1.3.2, last verified published stable 1.3.1. RELEASING.md still starts with v1.3.2 preparation.

The v1.3.2 GitHub release is now public, stable and immutable, published 2026-10-28 at 01:52:40 UTC, targeting the same commit. The README wording is accurate as a historical checkpoint; it is not an assertion that publication failed. Keeping that checkpoint as the primary installation status nevertheless makes readers resolve obsolete preparation information themselves.

Expected behavior

Current installation guidance should direct readers to current publication evidence, while historical preparation evidence and immutable release assets remain unchanged. The existing release procedure already calls for a separate publication record; apply and make that post-publication step easier to complete consistently rather than inventing an absent policy.

Scope and acceptance

• Update all four current README editions consistently: either use version-neutral release/PyPI links or a freshly verified published-version statement.
• Add a separate dated v1.3.2 publication record with exact commit and GitHub/PyPI evidence. Verify PyPI separately before asserting package availability; a GitHub release alone is insufficient.
• Preserve historical preparation snapshots, immutable tags/assets and the distinction between Python publication, Node Control deployment and independently managed skill updates.
• Make the post-publication documentation check explicit in the reusable release checklist, with no advance publication claim or automatic deployment.
• Run documentation/i18n and release-command/consistency tests.

Related work and verification limits

#281/#299 addressed the same class of documentation drift for v1.1.0 and are closed; this is the current v1.3.2 follow-up, not a duplicate of that completed version-specific work. Open/closed issues and PRs were reviewed. Source and current GitHub release metadata were checked on 2026-10-29. PyPI availability and tests were not independently checked in this review; no publication, deployment or immutable-asset change is requested by filing this issue.