docs: record stable 0.1.0 release

[tensornull]

What changed

• mark stable 0.1.0 complete across the roadmap, compatibility matrix, README, changelog, release guide, and repository agent contract
• record the exact release commit, CI and publish runs, bounded live smoke, npm dist-tags and integrity, OIDC provenance, signatures, and post-publication fixture evidence
• record the failed post-merge Release Please run, its retained unreviewed 0.2.0 branch, and the now-disabled RELEASE_PLEASE_ENABLED variable
• keep Repository Foundation in progress and 0.2 planned; this PR contains no 0.2 implementation work
• disclose the immutable npm tarball's candidate-era README and the deferred development-tooling audit findings while distinguishing the zero-finding production dependency audit

Why

Stable 0.1.0 is published and independently verified, but main still describes it as a candidate. This docs-only closeout aligns repository status with the immutable release and preserves the operational evidence and remaining Release Please maintenance boundary.

Verification

• git diff --check
• npm run format:check
• npm run lint
• npm run typecheck
• npm run check:public-preview
• npm audit --omit=dev --json (0 production vulnerabilities)
• npm run verify (12 files / 204 tests, package/examples/fixtures, minimum/locked/latest OpenAI 6.x, actionlint, standalone and self-contained gates)

Release evidence

• release commit: 1752cbb57f11dc6dca8dd1b13f0f8d5e8b5fdfca
• immutable Release: v0.1.0
• publish run: 30345735681
• npm: latest=0.1.0, next=0.1.0-alpha.3
• Release Please failure run: 30345116433; retained unreviewed branch commit 3f0949e5c0ccd0923d10595437f7a315f013af7c