Drop the README's claim to a release matrix that no longer exists

Drop the README's claim to a release matrix that no longer exists

80e61fbb21 removed the release-matrix admission path; the package README
still said the checked matrix owns release admission, contradicting its
own later statement that no release-evidence path exists.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoYpb8FEmdxVErsv7ABCYi

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoYpb8FEmdxVErsv7ABCYi

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

modified packages/agent-client-protocol-conformance/README.md

Diff

1 file changed, +4 -3

The Grok and Cursor fixtures are independently versioned beneath
`fixtures/peers`. Their provenance labels say exactly what they prove. The
current checked fixtures are source-derived synthetic evidence, not captured
binary transcripts and not release compatibility claims. The checked ACP-10
release matrix owns pinned real-binary release admission. Stable, unstable, and
vendor extension fixtures remain in separate namespaces.
binary transcripts and not release compatibility claims. The release-matrix
admission path was removed in `80e61fbb21`; this package has no
release-evidence path. Stable, unstable, and vendor extension fixtures remain
in separate namespaces.

Live initialize summaries retain only safe identity/capability keys. This
includes nested auth-capability keys so unavailable stable methods such as

25	25		`The Grok and Cursor fixtures are independently versioned beneath`
26	26		`fixtures/peers`. Their provenance labels say exactly what they prove. The
27	27		`current checked fixtures are source-derived synthetic evidence, not captured`
28		-	`binary transcripts and not release compatibility claims. The checked ACP-10`
29		-	`release matrix owns pinned real-binary release admission. Stable, unstable, and`
30		-	`vendor extension fixtures remain in separate namespaces.`
	28	+	`binary transcripts and not release compatibility claims. The release-matrix`
	29	+	admission path was removed in `80e61fbb21`; this package has no
	30	+	`release-evidence path. Stable, unstable, and vendor extension fixtures remain`
	31	+	`in separate namespaces.`
31	32
32	33		`Live initialize summaries retain only safe identity/capability keys. This`
33	34		`includes nested auth-capability keys so unavailable stable methods such as`