CatalogLock v0.3.0 — Complete Protocol-Surface & Trust-Context Locking

CatalogLock v0.3.0 — Complete Protocol-Surface & Trust-Context Locking

Stable identity is not stable capability. Stable capability is not stable implementation.

v0.3.0 expands CatalogLock from live MCP tool drift detection into a contextual protocol-surface and trust-evidence gate.

Highlights

• ARD v0.91-first resolution at /.well-known/ard.json, predecessor fallback kept explicit, and HTML rel="ard" support.
• Lockfile v3 fingerprints the ARD base context, resolution source, authority/trust posture and contextual MCP surfaces.
• MCP 2026-07-28 server/discover, tools, prompts, resources and resource templates are locked for every concrete Streamable HTTP remote and configured client profile.
• Authenticated/contextual profiles inject secrets from environment variables without persisting secret values.
• Optional prompts/get, resources/read and custom read-only extension probes lock content where operators choose to inspect it. tools/call is forbidden.
• Modern MCP JSON-RPC identity, resultType, cache metadata, pagination and Mcp-Name/Mcp-Method transport rules are validated.
• Invalid x-mcp-header tools are excluded while valid tools remain inspectable.
• Trust evidence now has explicit absent, present-unverified, unsupported, verified and invalid states.
• Byte-accurate SHA-256 attestation/provenance verification, canonical JWS verification, JWKS/did:web resolution and pluggable trust verifiers.
• Endpoint drift, discovery/capability drift, primitive additions/mutations, private-to-public cache widening and read-only probe drift receive explicit classifications.
• Release hygiene gates prevent node_modules, .test-dist, .release, secret files and other staging artifacts from entering the published tree/package.

Verification

The release is gated by the full local suite, clean Node 20/22/24 installs, typecheck/build, npm audit, package/tree leak inspection, official ARD v0.91 conformance and positive MCP 2026-07-28 interoperability against the current official TypeScript SDK source pinned to an immutable upstream commit, plus an explicit compatibility-boundary check against the npm-published SDK 2.0.0, before publication.

• Protocol-version rejections returned as JSON-RPC errors with id:null are now surfaced accurately instead of being misclassified as response-ID mismatches.