chore(release): prepare Registry Stack v0.11.0 beta-13

[jeremi]

Summary

Prepare Registry Stack beta-13 as version 0.11.0 from the already reviewed release/1.0 integration state.

• rolls workspace packages and public release documentation to 0.11.0
• adds the beta-13 manifest, release notes, and v0.10.0 to v0.11.0 upgrade exercise
• adds the v0.11.0 archived docset while preserving all historical docsets
• keeps the release artifact boundary at exactly eight supported artifacts
• documents registry-backed issuance and the removal of source-free declaration credentials
• includes the integrated developer-experience work from feat(registryctl): catalog maintained authoring journeys #411 and feat(editors): add Registry Stack YAML navigation previews #409
• retains the hosted publication and Solmara adopter-evidence hold explicitly

Frozen beta boundary

This packet does not start any new feature ticket. Stable 1.0 work remains deferred. The editor language server, VS Code extension, and Zed extension are source-installed previews, not beta release artifacts.

The manifest and v0.11.0 docset currently pin the reviewed integration base cb795ea3a09ba81df59c56520d1a4ad039c0fa79. After the cumulative release/1.0 merge to protected main, a narrow finalization PR will replace these interim references with the protected-main merge SHA before tagging v0.11.0.

Review and verification

Exact head: 11bfffaacda1db7767e062216b203f0497636645
Base: cb795ea3a09ba81df59c56520d1a4ad039c0fa79

Independent release review found no remaining findings after correcting hosted-evidence wording and adding a drift guard.

Passed locally:

• cargo metadata --locked --format-version 1
• cargo fmt --all -- --check
• cargo check --locked --workspace --all-targets
• cargo test --locked --workspace
• 55 release-tooling unit tests
• release manifest and seven-docset validation
• Relay and Notary OpenAPI drift checks
• documentation generation, 89 docs tests, and Markdown validation
• full documentation check across current and archived docsets
• SEO validation for 2,831 pages
• built-link validation for 455,133 internal links and assets
• cross-machine deterministic project-input golden test on the version-bumped tree
• 107 registryctl library tests, including embedded starter provenance
• git diff --check

The source beta may ship while hosted publication remains held. The hold is preserved in the manifest and public wording rather than being represented as completed evidence.

Signed-off-by: Jeremi Joslin jeremi@joslin.fr

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 11bfffaacd

ℹ️ 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]

Keep rollback proof reachable after issuance testing

When this procedure follows the candidate proof above, step 6/8 can create v0.11 credentials and the rollback section even tells operators to preserve issued verification material; this step then requires that no v0.11 issuance or other acknowledged state exists after the v0.10 recovery point and otherwise aborts to fix-forward. That makes the documented rollback proof unreachable for the same release-gate run that exercises issuance provenance, so the gate cannot demonstrate both issuance behavior and rollback unless issuance is isolated in disposable state or the recovery-point rule is clarified.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Pin the archive to the release-prep source

When the v0.11.0 archive is built, build-archives runs generation with DOCS_DOCSET=v0.11.0 and the repo-docs sync clones product docs at this ref for archived monorepo docsets. This commit is what adds the 0.11 release headings and versioned docs, but cb795ea... is the parent integration base, so the archived product pages will be generated from the pre-release-prep source (for example, release notes still under Unreleased) while the archive advertises v0.11.0. Pin this docset to the actual release-prep/tag-target commit before publishing the archive.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep install docs on an available release

The docs deployment workflow (.github/workflows/docs-pages.yml) runs on every push to main that changes docs/site/** or product docs, so this current tutorial can be published before the v0.11.0 tag workflow has created the tag and release assets. In that interval this first-run command fetches a non-existent tag or an installer whose downloads 404, breaking the public onboarding path; keep the live docs on the last published release or gate the docs publish until the tag and assets exist.

Useful? React with 👍 / 👎.