chore(release): prepare v0.22.0 beta-33

[jeremi]

Release identity

• Registry Stack v0.22.0
• Release train beta-33
• Based on protected main after v0.21.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-33 manifest bound to the current identifier catalog
• Product changelogs and v0.22.0 release notes
• Versioned docs docset, generated CLI reference, contract metadata, and archive identity
• First-registry-publication gates updated to v0.22.0

Verification

• Release planner: ready
• Release validators: current, docsets, source model
• Release test suite: 137 passed
• Advisory and workflow tests: 77 passed
• Docs tests: 24 passed
• Cargo metadata: locked and valid
• Local full release rehearsal: passed
• Canonical Ubuntu release rehearsal: run 31740376593, passed
• Independent high-effort release review: no findings

The Ubuntu archive identity is canonical because Pagefind's two native gzip streams differ across platforms. Two independent Ubuntu diagnostics reproduced the exact checked-in identity. Historical archive locks and v0.21.0 release records are unchanged.

Publication note

This release is the first intended npm/PyPI publication for the versioned client packages. The protected publication environments are configured, and registry publication remains an explicit release gate.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1d304eb886

ℹ️ 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".

[chatgpt-codex-connector]

Add the required DCO sign-off

When this release commit is submitted for merge, its trailer list is empty and contains no Signed-off-by entry, so it violates the repository's mandatory DCO policy and will fail DCO enforcement; recreate the commit with git commit -s before merging.

AGENTS.md reference: AGENTS.md:L272-L274

Useful? React with 👍 / 👎.