[DRB-2] Consolidate volatile package and product status claims

[metaphorics]

Residue family

Volatile product/package status duplication

Affected paths

• README.md:9,37-40,54-55,58,60 — pre-release 0.2.0, npm 0.1.0/0.2.0 wrapper status, five-target validation blocked by GitHub billing, unsafe Rust policy, formal proof caveat
• .agents/developer-audience-context.md:14,65-66,89 — operational status and key differentiators/trust signals copied from public docs
• docs/explanation/architecture.md:3,118-122 — pre-release 0.2.0, npm package status, five-target validation
• docs/explanation/verification.md:3-5,66,90-97 — pre-release/package status, 'every formal row is BLOCKING_FAIL' volatile snapshot, limits of current evidence
• npm/bamti-cli/README.md:9 — 'Version 0.1.0 is published on npm' (contradicts package.json version 0.2.0)

Source of truth

• Cargo.toml [workspace.package] version = '0.2.0'
• npm/bamti-cli/package.json and platform package package.json for package version and target claims
• npm registry metadata for bamti, bamti-cli, and @bamti/* for published version and artifact availability
• proof/completeness-ledger.json for current formal row status
• .outline/GATES.md and Justfile for release-gate state
• perf/hosts/bh1.toml for the exact supported performance host

Allowed edits

• Choose one public status owner: README.md keeps a concise, dated status paragraph; architecture.md and verification.md replace repeated status claims with links to README.md or the relevant manifest/ledger.
• Replace docs/explanation/verification.md:66 volatile 'every formal row is BLOCKING_FAIL' with a stable pointer to proof/completeness-ledger.json and the verification tooling.
• Remove or correct '0.1.0 npm packages do not contain prebuilt native artifacts' wherever registry evidence shows a different published version or artifact state.
• Remove or correct the 'five-target release validation blocked by GitHub billing' claim from evergreen explanation docs; keep it in one live blocker owner and refresh it against current evidence.
• Keep unsafe Rust policy and formal proof caveats in exactly one explanation doc each; elsewhere use short pointers.
• Update npm/bamti-cli/README.md:9 and any other package READMEs to match the manifest version and current registry state.

Forbidden guessing

• Do not invent npm download counts, package version numbers, or publication dates.
• Do not reclassify gate status from BLOCKING_FAIL to PASS (or vice versa) in prose.
• Do not hand-edit proof/completeness-ledger.json or verification/manifest.lock.json.
• Do not remove the pre-release caveat or published-artifact limitation without evidence that the state has changed.

Acceptance

• Exactly one document (README.md) carries the canonical public product status and pre-release notice; other docs link to it.
• Package version and artifact claims match the current npm registry, root Cargo.toml, and package package.json files.
• The 'five-target validation blocked' claim, if still true, appears in one live blocker owner, not in four documents.
• docs/explanation/verification.md:66 no longer embeds a volatile ledger snapshot.
• No document contradicts README.md, the package manifests, or proof/completeness-ledger.json.
• Synchronize documentation with integrated behavior #185's sync-docs pass finds no drift in package/status claims.

[metaphorics]

Dependencies

This issue is blocked by:

• Audit documentation rules and build surfaces #163 — Audit documentation rules and build surfaces
• Decide the published product facade #168 — Decide the published product facade
• Ground every repository release pin #183 — Ground every repository release pin
• Validate desktop packages and target evidence #180 — Validate desktop packages and target evidence

Parent: #156. Feeds: #185.