Audit release and distribution documentation consistency

[maruson08]

Problem

Release-facing documentation predates the GitHub v0.1.0 release and can imply future npm availability or release-candidate status.

Scope

• State that GitHub source, the v0.1.0 release, and its browser artifact are available.
• State clearly that the npm package is not published.
• Preserve same-origin vendoring with version, license, and SHA-256 verification.
• Keep Secure Tools integration explicitly future and avoid CDN guidance.

Acceptance criteria

• Distribution documentation matches the current release state.
• npm is not represented as available.
• GitHub v0.1.0 release and artifact availability are reflected.
• No speculative roadmap, package, build, artifact, or runtime changes.