Release 2.2.0

[heskew]

Version bump 2.1.2 → 2.2.0. Minor release — everything since v2.1.2 is additive; the one default-on surface (CIMD) is flagged below and has a disable knob.

Also introduces CHANGELOG.md (long overdue): Keep-a-Changelog format, backfilled from the GitHub release notes for every prior release (1.1.0 → 2.1.2), with the 2.2.0 entry matching the notes below. Added to the npm files allowlist so it ships in the tarball.

Verified at the bump: lint clean, prettier clean, full suite 1039 tests / 1037 pass / 2 pre-existing skips.

Draft release notes (for the GitHub Release, which triggers the npm publish)

Minor release — headless-agent (machine-to-machine) MCP authentication: the #159 train, plus key rotation.

• Signing-key rotation + multi-key JWKS publication (feat: signing-key rotation + multi-key JWKS publication (#128) #158, closes MCP OAuth: signing-key rotation + multi-key JWKS publication #128). Rotate the MCP signing key without invalidating in-flight tokens; JWKS publishes current + retiring keys.
• Client-assertion primitives (feat(mcp): client-assertion primitives — strict EdDSA verify + jti replay store #165): strict RFC 7523 private_key_jwt verification — EdDSA/Ed25519 via built-in node:crypto (no new dependency), jti replay store, ≤60s exp window.
• Client ID Metadata Documents (CIMD) (feat: Client ID Metadata Documents with SSRF-guarded resolution + consent interstitial (#166) #167): URL-shaped client_ids are resolved by fetching the client's metadata document through an SSRF-guarded, pinned-connection fetch, with a consent interstitial for interactive flows.
  • ⚠️ Default-on when mcp.enabled — URL client_ids are now accepted. Disable with mcp.clientIdMetadataDocuments.enabled: false, or restrict with mcp.clientIdMetadataDocuments.allowedHosts.
  • ⚠️ Interactive CIMD authorization requires browser cookies (per-flow __Host- consent cookie binds the interstitial).
• client_credentials grant (feat(mcp): client_credentials grant with CIMD-first private_key_jwt agents #170, closes client_credentials (2/4): CIMD-first client resolution for private_key_jwt agents (DCR back-compat optional) #161/client_credentials (3/4): token-endpoint grant — resource binding, per-grant TTL, discovery #162): headless agents authenticate as themselves with private_key_jwt — no browser, no human. CIMD-first client resolution; short-TTL audience-bound tokens; every issuance audit-logged.
• Rate limiting (feat(mcp): rate-limit client_credentials issuance and CIMD fetch attempts (#163) #171, closes client_credentials (4/4): rate-limit token issuance (defense-in-depth) #163): token issuance is limited per verified client_id (mcp.clientCredentials.rateLimit, default 30 req/min, false/0 disables — debited post-authentication so unauthenticated requests can't drain a client's quota), and CIMD document fetches are limited at a fixed 10 attempts/min per URL. Over-limit responses are 429 slow_down with Retry-After.
• Fix: client records use Harper's @createdTime instead of a hand-rolled created_at (fix: use Harper @createdTime instead of hand-rolled created_at #169).

After this merges

Tag + publish a GitHub Release v2.2.0 targeting the merge commit with the notes above — release.yml then lints/tests and npm-publishes @harperfast/oauth@2.2.0 to latest with provenance.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SerGP6Am3xz2CKyPgbRc73

[gemini-code-assist]

Code Review

This pull request updates the version of the @harperfast/oauth package from 2.1.2 to 2.2.0 in both package.json and package-lock.json. There are no review comments, and I have no feedback to provide.

[claude]

Reviewed; no blockers found.

[github-actions]

Reviewed; no blockers found.