chore(release): prepare v0.23.0 beta-34

[jeremi]

Release identity

• Registry Stack v0.23.0
• Release train beta-34
• Based on protected main after v0.22.0
• SemVer is minor because the release adds material product and distribution surfaces

Prepared surfaces

• Rust, Node, Python, OpenAPI, fuzz-lock, and generated-loader version identity
• Immutable beta-34 manifest bound to the current identifier catalog (51 active entries)
• Product changelogs and v0.23.0 release notes
• Versioned docs docset, generated CLI reference, contract metadata, and archive identity
• Release-scoped docs expectation updates for the new candidate docset

Archive identity

The v0.23.0 archive lock is bound to the canonical Ubuntu build. Pagefind ships
one WebAssembly search module per platform package, so wasm.en.pagefind and
wasm.unknown.pagefind are the only two files that differ between a macOS and a
Linux build of the same tree. Every other file in both trees is byte-identical,
and version_tree_sha256 is the same on both platforms. The second commit
records that Linux identity, as earlier release trains have done.

Client version-match threshold

The third commit keeps v0.22.0 in the four Evidence and Relay client READMEs.
That sentence records when exact client and deployment version matching began,
which is a fact about v0.22.0, not a restatement of the current version. The two
Discovery client READMEs and products/discovery/README.md keep v0.23.0,
which is when those packages start.

Verification

• Release planner: ready, 13 checks passed
• Release validators: manifest, docsets, archive lock, source model
• Release test suite: 68 + 21 + 30 + 3 + 12 + 8 passed
• Product gates: 16 passed (Evidence 6, Relay V2 6, Discovery, identifiers, Manifest, platform)
• Docs tests: 364 passed; npm run check: passed
• Cargo: fmt --check, check --locked --workspace --all-targets, clippy -D warnings, test --locked --workspace
• Evidence client bindings: Node (npm ci, build:debug, test, check:types, LICENSE) and Python (build, 47 tests, LICENSE)
• Canonical Ubuntu release rehearsal: https://github.com/registrystack/registry-stack/actions/runs/32313802637 (dispatched against the exact PR head)

Publication note

This release is the first intended npm and PyPI publication for the Registry
Discovery client packages. release/OPERATIONS.md requires the npm root and
platform package bootstrap and the PyPI pending trusted publisher for
registry-discovery-client to exist before the first v0.23.0 candidate is
requested. Neither is provisioned yet, so request-candidate must wait for that
one-time maintainer step.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 60915a167d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".