docs: sync to v0.4.0 and record what the release did and did not verify

[mbeacom]

The post-release docs sync for v0.4.0, following the #81 pattern: it lands after the release rather than riding the version bump, because a status block claiming "v0.4.0 on npm" before the tag is pushed is briefly false.

Both claims are now true. v0.4.0 published 2026-08-08 at 22:25:39Z; dev.adrkit/mcp re-published to the MCP registry at 23:16:38Z with isLatest: true; v0 moved to c3dff3a.

Version strings

README status block, CLAUDE.md, the site hero, the homepage status band, quickstart, the CI guide's pin advice, and the bug-report template placeholder. The CI guide's "currently the v0.3.0 commit" note now names c3dff3a, which is where v0 actually points.

The status blocks say the rung, not just the number

Markers landed at ADR-0014 rung 1 — unit, contract and purity coverage plus maintainer verification, with no reference-repository run. Every other surface the README and CLAUDE.md describe sits at rungs 1–2. Moving the version number without that clause would silently promote the newest and least-verified feature to the evidence level of the oldest, which is the failure mode ADR-0016 exists to catch.

CLAUDE.md also gains a markers section covering the two properties that are load-bearing and easy to break: that they reach adr explain and nothing else, and that the dedicated-line rule plus observed-byte truncation are what stop a marker from naming a record the file never declared.

DISTRIBUTION.md — regenerated, not patched

The 0.4.0 registry record is written from the fields the response actually returned, and the §A5 snippet is replaced with packages/mcp/server.json verbatim rather than having two version strings edited.

That mattered. The two had already drifted: the doc described ADRKIT_MCP_CWD as "Repository root to read (default: process.cwd())" while the shipped manifest says it must contain a readable .git entry. A version-string patch would have left that wrong for another release.

RELEASING.md — three new carry-forwards

The v0.3.0 notes stay; these are added because each one cost real time this cutover:

• bun.lock records a version per workspace package and nothing refreshes it. Neither bun install nor bun install --force updates those fields after a manifest bump. release-pack catches it (@adrkit/evaluator must resolve @adrkit/core to 0.4.0, got 0.3.0), and regenerating the lockfile fixes it while pulling unrelated drift (jose, undici, @octokit/*, @types/node) into the release commit. Edit the four lines directly.
• CLI_VERSION and SERVER_INFO are hardcoded and move with the manifests. Each has a test, so bun test finds them — step 1's "update any inter-package expectations" is mostly these two.
• The publish dry-run fails on the adapter (The publish dry-run skips the idempotency check, so it tries to republish a released adapter #104), now that an independently versioned package rides along in a lockstep pack.

The reference-verification index is annotated, not edited

Its rows record runs that happened against @adrkit/cli@0.3.0. Rewriting them to 0.4.0 would manufacture evidence for a run nobody performed, so they stay exactly as they are — the same reasoning that leaves specs/** and the changelog's history alone.

What is added is a dated note, because I checked the gate rather than assuming: the reference workflow pins ADRKIT_CLI_VERSION: "0.3.0" deliberately, so it is green rather than stale-and-red and PIN-3 still matches. But green against a superseded CLI is not evidence about the current release, so the note scopes the rung-2 verdict to @adrkit/cli@0.3.0 and flags the pin bump as separate work.

Verification

Step	Result
bun test	1840 pass, 0 fail
bun run lint	clean
adr lint	21 records, 0 errors, 0 warnings
site build	31 pages, complete

Not in this PR

• Bumping ADRKIT_CLI_VERSION in the reference repository and recording a fresh rung-2 run against 0.4.0.
• The publish dry-run skips the idempotency check, so it tries to republish a released adapter #104, the publish dry-run gap.

[Copilot]

Pull request overview

Synchronizes documentation with the v0.4.0 release and accurately scopes its verification evidence.

Changes:

• Updates public version references and Action pins.
• Documents inbound @adr markers and rung-1 status.
• Records release lessons and registry/reference-verification state.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates release status and marker evidence.
CLAUDE.md	Documents marker constraints and scope.
docs/DISTRIBUTION.md	Refreshes MCP registry records and manifest.
docs/RELEASING.md	Records v0.4.0 release guidance.
docs/reference-verification-spec-kit-extension.md	Clarifies evidence currency.
site/src/components/Hero.astro	Updates homepage version.
site/src/content/docs/index.mdx	Updates status band.
site/src/content/docs/quickstart.mdx	Updates published CLI version.
site/src/content/docs/ci.mdx	Updates release and Action pins.
.github/ISSUE_TEMPLATE/bug_report.yml	Updates version placeholder.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.