chore(release): prepare v0.17.0

[mbeacom]

What and why

Releasing #257 so it reaches people using the Action. Until v0 moves, packages/ci@v0 consumers still get the old governing-decisions comment.

I went with a minor release rather than a patch. The comment body isn't a documented contract, so 0.16.1 would have complied with RELEASING.md. But the proposals and history headings moved into collapsed <summary> lines, and anyone scraping posted comments for them breaks. A minor release lets the notes call that out.

• Lockstep bump to 0.17.0: the four packages, CLI_VERSION, SERVER_INFO, server.json, and bun.lock's workspace entries (edited directly, per the v0.4.0 note).
• Documented pins: README, ci.mdx, badges.mdx, quickstart, hero, index.mdx, RELEASING.md, AGENTS.md, and the bug-report template. The <0.16.0 mentions left in RELEASING.md and the Spec Kit verification doc are the historical Spec Kit range, not ours.
• CHANGELOG: [Unreleased] → [0.17.0] - 2026-10-03, plus compare links. It says the npm packages carry no behavior change and flags the heading move.

Checklist

• Commits are DCO signed off (git commit -s).
• If this changes a recorded decision in docs/adr/, an ADR is added or supersedes the affected record. (None.)
• If the schema changed, I edited the Zod source and re-emitted. (Unchanged.)
• If packages/ci/src or @adrkit/core changed, I regenerated packages/ci/dist. (Neither changed here; the bundles are byte-identical to main.)
• New or changed behavior is covered by tests. (Version-only; the existing CLI_VERSION/SERVER_INFO tests assert the new values.)
• bun run typecheck && bun run build && bun test && bun run lint pass (3216 tests). check:changelog and check:doc-pins pass, and release:pack prepared all five packages for v0.17.0 with no lockfile drift.

Notes for reviewers

• If this merges on a later day, adjust the CHANGELOG date.
• After merge, the rest is the usual cutover: tag v0.17.0 → Release publishes npm and drafts the GitHub release → I publish the draft (Marketplace selection) → v0 moves and the container publishes. The MCP registry entry needs a manual mcp-publisher re-publish at 0.17.0, as with every release.

[Copilot]

Copilot review overview

🟡 Changes recommended

The changelog still records October 2 even though the stated release-date policy now requires October 3.

Review effort: Balanced
Findings: 1

Open (1)

• Update release heading to the actual cutover date · New

What changed in this PR

Prepares the lockstep v0.17.0 release so the updated governing-decisions Action reaches consumers.

Changes:

• Bumps four packages, runtime constants, registry metadata, and lockfile entries.
• Updates documentation and examples to v0.17.0.
• Adds release notes for PR #257.

Decision compliance could not be queried because the adrkit MCP tools were unavailable.

File	Description
site/​src/​content/​docs/​quickstart.mdx	Updates published version.
site/​src/​content/​docs/​index.mdx	Updates status banner.
site/​src/​content/​docs/​ci.mdx	Updates immutable Action pins.
site/​src/​content/​docs/​badges.mdx	Updates CLI pins.
site/​src/​components/​Hero.astro	Updates hero version.
README.md	Updates Action guidance.
packages/​mcp/​src/​server.ts	Bumps MCP server version.
packages/​mcp/​server.json	Bumps registry metadata.
packages/​mcp/​package.json	Bumps MCP package.
packages/​evaluator/​package.json	Bumps evaluator package.
packages/​core/​package.json	Bumps core package.
packages/​cli/​test/​color.test.ts	Updates version assertion.
packages/​cli/​src/​index.ts	Bumps CLI runtime version.
packages/​cli/​package.json	Bumps CLI package.
package.json	Bumps root lockstep version.
docs/​RELEASING.md	Updates current-release references.
CHANGELOG.md	Adds v0.17.0 release notes and links.
bun.lock	Aligns workspace versions.
AGENTS.md	Updates public-version status.
.github/​ISSUE_TEMPLATE/​bug_report.yml	Updates version placeholder.

[github-actions]

Decisions governing this change

22 accepted decisions govern this change · 2 historical records

Show all 22 governing decisions and why each applies

• 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: README.md
  • 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/**
• 0036 — Expose the governing-decisions Action through one root Marketplace entry point
  • via path: docs/RELEASING.md
• 0037 — Treat generated knowledge systems as downstream read models, not decision authorities
  • via path: README.md
  • via path: site/src/content/docs/**
• 0038 — Offer the bootstrap decision record as an offer rather than a backfill candidate
  • via path: site/src/content/docs/quickstart.mdx
• 0039 — Derive a valid-time window from date and supersession, and resolve a git ref at the CLI boundary
  • via path: packages/cli/src/index.ts
• 0040 — Keep derived surfaces in lockstep with three mechanisms matched to three classes of drift
  • via path: AGENTS.md

Historical records that once covered this change (2)

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

_{Links point at 00fb091, this run's GITHUB_SHA. Run adr explain <path> locally to see why a file is governed.}