docs: 1.0.0-rc.6 is the published release candidate

Cut from 265def6 to all four registries — npm 1.0.0-rc.6 (dist-tag next),
PyPI 1.0.0rc6, NuGet 1.0.0-rc.6, Maven Central 8.0.0-rc.6. The tag's annotation
carries the coordinates and why the candidate exists; this line is the one an
agent reads first.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTcEKXTQMYt84fAjuw5A2M

Author: dmealing

AGENTS.md

@@ -36,7 +36,7 @@ in ADR-0035 **Amendment 3**. Do not reintroduce a waiting gate in any form.
 
 **Where the versions are.** `latest` on every registry is **`0.25.0`** (npm / PyPI / NuGet) ·
 **`7.25.0`** (Maven Central, aligned `minor.patch` on its historical major `7` — the Maven
-major is always **npm major + 7**). The **`1.0.0-rc.5`** release candidate is published on all
+major is always **npm major + 7**). The **`1.0.0-rc.6`** release candidate is published on all
 four, on npm's `next` tag. `metamodelVersion` on `main` reads **`1.0`**: C4's freeze has
 landed. Per-release detail lives in **`CHANGELOG.md`** — it is the log, and this file does not
 duplicate it.