[abruption]

The public 0.1.0 archive retains pre-publication README wording, while current validation/release notes still describe the stable release as pending. Record the actual publication, artifact identity and verification scope; distinguish historical candidate/live evidence and document the immutable archive discrepancy. All four READMEs now explain the differing CI depth, the discovery→dry-run→submit→ACK sequence, and the planned-feature boundary.

Add a required manual review of the exact packaged multilingual documentation to the release runbook, including versioned filenames and approval evidence. Automated hash/file-list checks alone do not establish prose accuracy. Closes #35; related to #33 and #34.

Validation:

• Public registry tarball SHA-256/SHA-512 match the 0.1.0 staging manifest; source/run and publication time checked.
• Repository documentation/link contract and git diff --check pass.
• npm run test:package passes (repeat pack, isolated install/types/uninstall).
• Final local tarball contains all six documents byte-for-byte as reviewed; dist/* and package.json match published 0.1.0 byte-for-byte. This local archive is only a documentation packaging check, not a new release.
• npm's version page returned HTTP 403; rendered README state was not verified.

No runtime, version, workflow or registry mutation is included. The already published 0.1.0 tarball will keep its old documents; a separately prepared and approved later version is required to ship corrected packaged documentation.