fix: verify registered software admissions and bind measured issuance evidence

[abrichr]

The release verifier now sends registered software-ed25519-dsse-v1 bundles through the existing public-trust verifier. These bundles previously fell into the GitHub-attestation path. The correction preserves the registered keys, exact subject bytes, issuer/ref/environment constraints, and current authority and revocation checks. Profiles that require GitHub CLI still require version 2.98.0.

The measured admission adapter checks one exact workflow bundle against retained trial reports, installed and published package bytes, contract openings, and SQLite idempotency records. Each trial must match its original observation row and native reports. It requires all six declared classes and rejects missing evidence or counters. Private recordings, recipes, and trial data stay outside this repository.

Signing uses the existing authority and a reviewed plan hash. Persistent request journals prevent an uncertain issuance from being retried under another handle. The staged workflow keeps storage references distinct from protected-main issuer sources; its README describes each phase and read-only reconciliation. This PR doesn't issue an admission.

The live Flow 1.34.0 check exposed an invalid historical reference and correctly refused it. Its signed acceptance-summary reference names registry revision 1 at commit 2c129702da718522cc257913207b6ed6f3b33b7c, with head 9a9f597b0d87674c4d36c022227201a5d8f3072237624346793692c3a863d12e. That immutable commit contains an empty registry with head 3c88a4e945f1aa51ee080f05331c0d7a36b907ad288cf8a24b2fef08b1681a97. An independent fetch of the exact public bytes and a strict replay through unchanged fetch_pair() both returned reference registry revision or head differs. The historical signed records remain unchanged. A new admission must bind real containing commits before it can yield a valid receipt.

Validation: 98 focused tests pass across the adapter, registered-profile routing, public trust, issuer, and production trust suites. Independent review repeated the routing tests and exercised real registered signatures and current trust state without a keyless fallback. The adapter review also confirmed that exchanged report references, mismatched native idempotency keys, and inconsistent SQLite reservation records refuse. Both required profile checks pass at 6eef685308a8c581905135e3e845c93b4a6754cc.