Release summaries
cli-mcp-consumer-enablement
Decommission the hosted ContractSpec MCP (api-library /mcp/* and /api/mcp/* docs/cli/ internal/contracts endpoints) and ship two local offline-first stdio MCP servers in the CLI: `contractspec mcp` (knowledge + author tools, fully offline, with a new contracts.create scaffold) and `contractspec mcp --runtime` (fail-closed projection of the consumer's own contracts). bundle.library's MCP builders become transport-agnostic.
maintainer
api-library loses its MCP handlers (mcp-handler.ts, contracts-mcp-services.ts) and their wiring — zero hosted MCP compute; GraphQL/webhooks/control-plane/channel handlers are unchanged. cli-contractspec gains a `mcp` command with a default knowledge+author server and a `--runtime` projection server under src/ai/mcp/* (runtime/* projects only OperationSpecRegistry.listBound() ops behind a fail-closed decide). bundle.library exposes buildDocsMcpRegistries/buildCliMcpRegistries/ buildInternalMcpRegistries/buildContractsMcpRegistries plus a contracts-first contracts.create defineCommand (+ createSpec on ContractsMcpServices); existing Elysia handlers are unchanged (web-landing still serves docs MCP over HTTP).
integrator
The hosted api.contractspec.io MCP endpoints are gone — repoint editors/agents at the local CLI MCP servers. `contractspec mcp` is offline and needs zero setup; `contractspec mcp --runtime` projects this repo's contracts as MCP tools, allowing read-only queries and denying writes/commands by default (opt in via .contractsrc.json mcp.runtime.allowWrites; override discovery via mcp.runtime.registry). The mcp.runtime keys are read raw and not yet in contractsrc.schema.json (no autocomplete — v1 limit).
