docs: record stable 0.1.1 release

[tensornull]

Summary

• record stable 0.1.1 and Repository foundation as complete across the public documentation
• preserve the exact Release Please, immutable Release, bounded live-smoke, npm OIDC, registry, integrity, signature, and provenance evidence
• distinguish the disclosed one-time main-context publication recovery from the permanent immutable-tag-bound workflow
• codify the exact-head review identity, release freeze, Environment-policy, and no-bypass rules in the repository runbook and AGENTS.md

Why

The package is now published as cometapi@0.1.1, but the repository still described it as an unpublished candidate. The closeout also needed to record the real recovery provenance without claiming that the permanent tag-bound route had already completed an end-to-end registry publication.

Validation

• clean exact-HEAD npm run verify (477 tests, package/publint/ATTW, examples, ESM/CJS/OpenAI-host fixtures, minimum/locked/latest OpenAI 6.x, actionlint, and copied standalone verification)
• npm run test:secrets
• npm run check:standalone-content
• npm run check:public-preview
• independent adversarial documentation/workflow-contract review
• current GitHub variables, npm Environment tag:v* policy, immutable v0.1.1 Release, npm dist-tags, integrity, and shasum read back without drift

[tensornull]

Owner exact-head audit completed for 392895a after all required CI passed. This COMMENTED review records the audit under the zero-required-approval ruleset; it is not an APPROVED review because the reviewer and PR author are the same account.