docs: reconcile published release records and packaged README review #35

Published session-peer@0.1.0 still contains pre-publication README/validation wording in its immutable tarball. GitHub README PR #15 corrected source documentation but cannot change that archive. Current VALIDATION.md and RELEASING.md also describe stable publication as pending, and all four READMEs summarize cross-platform CI without distinguishing its depth.

• Record the actual 0.1.0 public release time, source/run, artifact digest and verification scope, preserving historical candidate/live evidence.
• Document the immutable 0.1.0 tarball README discrepancy and require review of the exact packaged multilingual README/install/version/CI wording before the next stage approval. Same-version republishing is not a remedy.
• Distinguish macOS/Linux full contract/package checks from bounded Windows native smoke on Node 22/24 in all four READMEs.
• Put discovery, dry-run, one intended submission and separate receiver ACK observation together, with no-reply/exit uncertainty explained; link planned gaps to docs: maintain Python parity matrix and npm migration guide #33.

Related: #33 (full parity/migration matrix), #34 (future Windows coverage expansion). This change corrects current documentation; it does not implement planned parity features or authorize publication. Review correlation: STS-README-REVIEW-20260928.

Evidence: stable staging run, current source, public registry/tarball read-only check on 2026-09-28 KST. SHA-256: 41189d771a94c14775f8ef297d887627f4ab12819856bb18efff291e03c2e269. npm web page returned HTTP 403 to the reader; rendered page state was not verified.