chore(release): prepare Registry Stack v0.41.0

[jeremi]

Summary

Prepare Registry Stack v0.41.0 beta-53 from protected main. Record every BREAKING item since v0.40.0 in the release note and site changelog, and rewrite the upgrade guide for the required v0.40.0 to v0.41.0 migration steps. The covered changes include both BReg historical-state refusals, client runtime floors, task-grant status and deferred grants, original receipts, local BReg/Casework claim mapping, and retired compatibility paths.

Date the product changelogs and add the manifest with its exact identifier catalog binding. Generate the candidate docset and archive lock through the maintained canonical container and archive snapshot generator, preserving human review dates and CLI publication metadata. Correct the Scheduling changelog to state that offline mode checks remaining lifetime and also admits the final 900 seconds of a deferred grant without checking revocation. Pass the required authored project to schedulingctl check PROJECT --runtime-config FILE; verify the sibling plan, apply, and status forms against their Clap definitions.

Evidence

• uv run --no-project --with PyYAML==6.0.2 python release/scripts/registry-release prepare --version 0.41.0 --release-id beta-53: exit 0, all 13 checks ready.
• uv run --no-project --with PyYAML==6.0.2 python release/scripts/registry-release validate release/manifests/registry-stack-beta-53.yaml and uv run --no-project --with PyYAML==6.0.2 release/scripts/check-release-source-model.sh: exit 0.
• uv run --no-project --with PyYAML==6.0.2 python -m unittest release/scripts/test_registry_release.py release/scripts/test_registry_release_plans.py release/scripts/test_release_notes.py release/scripts/test_prepare_release_docs.py release/scripts/test_release_rehearsal.py release/scripts/test_check_release_source_model.py: exit 0, 191 tests.
• Canonical Ubuntu 24.04 documentation preparation and maintained node scripts/archive-lock.mjs snapshot v0.41.0 refresh, guarded by the authoritative absent-tag and current-candidate immutability checks: exit 0, 690 tests passed with no skips, full docs check passed, 253,692 links checked, and 48 total archive locks checked, with all 47 preexisting locks preserved. The regenerated archive SHA-256 is 4f948c5abe4103dcd268905fde5d17527054f44a9e0616dd847664a53a9d1e54.
• Complete strict read-only release rehearsal passed all 10 jobs on the exact corrected head. The previous rehearsal is superseded as current-head evidence. The rehearsal covers the future-tag archive, canonical Linux shards and smokes, image onboarding and baseline metadata, and both Linux Node architectures. The evidence-producing rehearsal and baseline renewal landed separately in chore(release): renew v0.41.0 image advisory evidence #2022; the candidate will rescan its own images.
• git diff --check: exit 0. Independent source and changelog review covered every BREAKING entry and confirmed that review dates are preserved.

Notes

The workspace is already 0.41.0. Advisory evidence was renewed separately in #2022. The fresh automatic predecessor upgrade rehearsal passed on the corrected head. This PR must merge through the queue alone. It covers BReg, Casework, Evidence, and Messaging; Scheduling state remains outside that rehearsal. The numbered candidate remains the first hosted proof combining standalone Linux arm64 Zig builds, the glibc 2.34 floor, and Go 1.27.2.

PRs #1956, #2018, #2019, and Dependabot are excluded. Solmara adaptation, the Debian builder Go package, merge queue concurrency, and the 1.0 promise remain owner decisions or deferred work. Publication environment approvals remain with Jeremi.

DCO

• Every commit includes a Signed-off-by trailer.
• I reviewed the submitted changes and am responsible for the contribution.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-13T01:04:12.230938Z	16c0217	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 16c0217a72

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