Release v0.12.0

[mbeacom]

Cuts the unreleased changelog into ## [0.12.0] - 2026-08-27 and moves every lockstep version-bearing surface from 0.11.0 to 0.12.0. Release preparation only — no new features and no unrelated fixes.

What v0.12.0 actually matures

Six commits landed since v0.11.0, and they are mostly about making this repository's own guarantees enforceable rather than aspirational.

• The gates that certify a pull request now execute from the default branch (feat(ci): execute the gates that certify a pull request from the default branch #179, ADR-0035). trusted-gates.yml runs on pull_request_target, so the workflow file, its referenced actions, and the actions/checkout commit all come from main rather than from the branch under review. trusted-dco is the authority for sign-off; gate-integrity blocks changes to gate-defining paths without a maintainer acknowledgment that is dismissed on every event that can move the head or the base. Scope is stated rather than overstated: this does not make the advisory ci.yml gates tamper-proof, and the unprotected routes are enumerated and pinned by a test.
• Those gates are now deployed, required, and observed failing (docs: record deployed trusted-gates evidence #180). trusted-dco and gate-integrity are among the ten required contexts on the main ruleset, and the pull-request-controlled dco context was removed from that set only after the trusted one reported green on real pull requests. gate-integrity went red before an acknowledgment and green after it on three ordinary pull requests; trusted-dco went red on a commit that deliberately omitted Signed-off-by and green once it was signed. Deployed evidence in both directions, per ADR-0016 — not a fixture.
• A guarded recovery path for the moving v0 Action tag (feat(release): add guarded Action tag recovery #175, The moving v0 Action tag has no documented rollback path #136, docs(releasing): no rollback procedure for the moving v0 Action tag #122). Recovery accepts only a stable release whose annotated tag peels to a commit on main, whose exact Release run succeeded, whose root version matches, and whose committed Action bundles exist. It pushes under a lease and leaves a durable withdrawal marker so the removed commit cannot be republished on a rerun.
• MANIFEST.md's decision-corpus inventory is generated and gated (MANIFEST.md inventory drifts silently: generate it from the corpus instead of hand-maintaining it #131, Scope how derived surfaces stay in lockstep with the corpus (CLI, workflows, guards) #132). It had drifted six records before anyone noticed. bun run emit:manifest renders it from adr graph --format json, and clean-clone-builds regenerates it and asserts no diff. The CLI stays read-only; the writing lives in a repo-local script.
• Marker scan health and unbound claims surface in the CI comment (Surface marker scan health and dangling claims in CI comments #178, Surface marker scan health in the rendered PR comment, not just the Action log #112, A dangling @adr marker is invisible in the rendered PR comment, even when the scan was completely healthy #126) — changed files that were absent, unreadable, out of tree, or skipped, reported separately from @adr claims that read cleanly but bound to nothing in this corpus. Bounded, escaped, advisory, ordered behind changed-record errors.
• Inbound marker amplification is bounded before resolution (Bound the number of markers one scan can produce #113) — 64 declarations per file, 10,000 per batch, in deterministic code-unit path plus source order, collapsing into one advisory finding. PR-authored markers still gain no exit-code authority.
• adr queue no longer stays silent on a reviewed record with no routing tier (adr queue stays silent when a proposed record has a deadline but no routing tier #111). The spec's carve-out is two-conditioned; only the first condition was implemented, so a cross-team record with reviewBy and no review block was listed with tier=None and no finding at all. Severity stays info, so no exit code changes.

Two changelog corrections, not a mechanical rename

The trusted-gates trio was authored under ### Added in #179, but #177 later inserted a ### Fixed heading above it and silently swallowed all three entries into the wrong section. They are restored to ### Added, and ### Fixed now follows ### Changed as in every prior release section.

The docs/repository-trust-operations.md entry claimed those controls "cannot be applied until this lands." That stopped being true when #180 recorded the deployed state, so the entry now says what is actually deployed. Every other entry is carried across verbatim, with no duplicates and no upgraded evidence-rung wording.

Versions

Surface	Before	After
root, @adrkit/core, @adrkit/evaluator, @adrkit/cli, @adrkit/mcp	0.11.0	0.12.0
CLI_VERSION, SERVER_INFO, both packages/mcp/server.json fields	0.11.0	0.12.0
bun.lock (four workspace version lines)	0.11.0	0.12.0
@adrkit/spec-kit	0.1.3	0.1.3 — unchanged
agent plugin (packages/adapters/agent-plugin)	0.2.0	0.2.0 — unchanged

Both adapters are independently versioned under ADR-0007 and deliberately do not move with the repository release.

bun.lock's diff is exactly the four workspace version lines, edited directly rather than by regenerating the lockfile, so no transitive drift rides along in the release commit. The version-narrative sweep covers AGENTS.md, docs/RELEASING.md, the bug-report template placeholder, and all five site surfaces including the deliberately pinned @adrkit/cli@0.12.0 badges recipe.

Validation evidence

Every command below was run against this branch.

Check	Result
bun install --frozen-lockfile	clean, no lockfile drift
bun test	2790 pass, 1 skip, 0 fail (194 files, 37526 assertions)
bun run typecheck / bun run lint	pass
bun run adr lint	35 records, 0 errors, 0 warnings
actionlint	clean across all 7 workflows
check:deps, check:freeze-hashes, check:doc-pins, check:clause8, check:no-spike-heuristics, check:site-grammar, check:changelog, check:clean-clone, check:dco	all pass
schema:emit + git diff --exit-code schema/adr.schema.json	clean
emit:manifest + git diff --exit-code MANIFEST.md	clean — already matched the corpus (35 records)
git diff --exit-code packages/ci/dist	clean
Action bundles vs canonical Linux Bun 1.3.14 rebuild	index.js and queue-action.js byte-identical
bun run release:pack -- --tag v0.12.0	5 artifacts: core/evaluator/cli/mcp at 0.12.0 + spec-kit at 0.1.3
Installed-tarball smoke, Node 22.22.2	pass
Installed-tarball smoke, Node 24.16.0	pass
bun run release:publish -- --dry-run	exit 0; @adrkit/spec-kit@0.1.3 already matches; skipping
spec-kit registry vs packed shasum	bb9eb41076dba85c8c1dc6f86fa293a6d0a2e14c on both sides — the real run will skip it
npm audit over .release/smoke (all 5 packed artifacts)	0 vulnerabilities, reconciled against an empty KNOWN_CONSUMER_ADVISORY_ACCEPTANCES
bun run audit:gate (workspace scope)	pass — 0 high, 0 critical
OCI --target adrkit and --target mcp build	both succeeded
scripts/smoke-container.mjs on the MCP image	served both MCP protocol eras
All-in-one selectors cli / adr / adrkit	all report 0.12.0; ci and queue-action resolve; adr lint and adr queue --format json run read-only and networkless against a :ro mount

Two notes worth carrying into the next cutover, both already-documented hazards that fired here:

• release:pack runs a non-frozen bun install and rebuilds, and local Bun 1.4.0 rewrites unrelated runtime helpers throughout both committed Action bundles. They were restored to the canonical Bun 1.3.14 output and re-verified byte-identical. @adrkit/ci is private and absent from the release manifest, so the packed tarballs are unaffected.
• The The publish dry-run skips the idempotency check, so it tries to republish a released adapter #104 dry-run failure on the adapter is gone — the release-publish change that shipped in v0.11.0 makes the dry run skip registry-identical artifacts, and it did so here.

Not done yet — deliberately

This PR prepares the release and nothing more. No v0.12.0 tag has been created or pushed, no npm package has been published, the moving v0 Action tag has not moved, and nothing has been pushed to GHCR. Those happen only after this merges, via the normal protected Release workflow and its downstream Publish container run, followed by the manual MCP registry re-publish — docs/RELEASING.md, "Subsequent releases" steps 6 through 10.

Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com

[github-actions]

Decisions governing this change

• 0003 — Ship as a Spec Kit extension plus a standalone CLI, not a competing harness
  • via path: packages/cli/**
• 0007 — Isolate integrations as optional adapters and build only against public surfaces
  • via path: packages/*/package.json
• 0010 — Use Bun as the package manager and test runner while publishing Node-targeted artifacts
  • via path: package.json
• 0011 — Host the canonical JSON Schema at its $id on adrkit.dev
  • via path: site/**
• 0016 — Require every check to be observed failing before it counts as coverage
  • via path: packages/*/test/**
• 0017 — Keep dependency audit scope explicit and release-scoped
  • via path: packages/*/package.json
• 0018 — Adopt MCP SDK v2 and serve protocol revision 2026-07-28 dual-era
  • via path: packages/mcp/**
• 0022 — Scan inbound markers in check and CI without giving them exit-code authority
  • via path: packages/cli/src/index.ts
• 0024 — Report the measured scan extent, not the window constant
  • via path: packages/cli/src/index.ts
• 0025 — Ship badges as recipes over existing output, not a new CLI surface
  • via path: package.json
  • via path: site/src/content/docs/badges.mdx
• 0026 — Identify the CI comment by the strongest author evidence the token allows
  • via path: site/src/content/docs/ci.mdx
• 0027 — Ratify the deterministic evaluator and bind calibration reporting to the first probabilistic pass
  • via path: packages/evaluator/**
• 0029 — Scope Backstage publication as a downstream consumer, tiered on the entity-ownership mapping
  • via path: packages/cli/src/index.ts
• 0030 — Keep extension surfaces that carry a dependency tree outside this repository
  • via path: package.json
• 0031 — Publish a narrow consumer SDK as the contract, and document the CLI JSON as its sibling
  • via path: docs/RELEASING.md
  • via path: packages/cli/src/index.ts
• 0032 — Publish one lockstep OCI image after the coordinated release succeeds
  • via path: docs/RELEASING.md
• 0033 — Select interactive graph presentation at the CLI boundary while preserving piped DOT
  • via path: packages/cli/src/index.ts
  • via path: site/src/content/docs/**

Historical records that once covered this change

These no longer bind this change, and are listed for context only:

• 0005 — Gate proposals with a deterministic-first evaluator and declarative escalation (superseded) — superseded by 0027
  • via path: packages/evaluator/**
• 0021 — Resolve inbound source annotations without changing the schema (superseded) — superseded by 0022
  • via path: packages/cli/src/index.ts

[Copilot]

🟢 Approval recommended

The lockstep release surfaces are consistently aligned, independent adapters remain unchanged, and the release documentation and validation evidence are complete.

Pull request overview

Prepares the coordinated v0.12.0 release while preserving independently versioned adapters.

Changes:

• Bumps all lockstep package, runtime, registry, lockfile, and test versions.
• Finalizes the v0.12.0 changelog with corrected section placement and evidence.
• Updates release documentation, site surfaces, and issue templates.

File summaries

File	Description
package.json	Bumps the root version.
bun.lock	Aligns four workspace versions.
CHANGELOG.md	Cuts the v0.12.0 release section and links.
AGENTS.md	Updates current release status.
docs/RELEASING.md	Updates current lockstep release references.
.github/ISSUE_TEMPLATE/bug_report.yml	Updates the version placeholder.
packages/core/package.json	Bumps @adrkit/core.
packages/evaluator/package.json	Bumps @adrkit/evaluator.
packages/cli/package.json	Bumps @adrkit/cli.
packages/cli/src/index.ts	Updates the bundled CLI version.
packages/cli/test/color.test.ts	Updates the version assertion.
packages/mcp/package.json	Bumps @adrkit/mcp.
packages/mcp/src/server.ts	Updates MCP server metadata.
packages/mcp/server.json	Updates both registry version fields.
site/src/components/Hero.astro	Updates the displayed npm version.
site/src/content/docs/index.mdx	Updates project status.
site/src/content/docs/quickstart.mdx	Updates the published-version callout.
site/src/content/docs/ci.mdx	Updates Action tag guidance and commands.
site/src/content/docs/badges.mdx	Updates pinned CLI recipes.

Review details

• Files reviewed: 18/19 changed files
• Comments generated: 0
• Review effort level: Balanced

---

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