runtime 4.0.6 + v6.1.1 distribution: staged, gated, live-qualified - #122
Merged
Conversation
Imports the signed/notarized provider runtime 4.0.6 (source 78aefe2f, all nine release-evidence gates true; notary cce3ec9a). Wire contract advances ee98d75b -> 4de687b8: advisory response additively widened for failure-text salvage (completeness, salvaged_from, one new reason enum); 12-action set and authority/artifact contracts unchanged. Version surfaces moved together: client pin 4.0.6, schema consts (version + wire digests, positive/negative-validated), plugin 6.1.1 (first tagged publication of the merged-but-untagged 6.1.0 skills), marketplace + skills regenerated, pinned tests, READMEs, migration doc, release-shaped fragment. Staged qualification: readiness ok (54 ready; codex non-ready set IDENTICAL to the installed 4.0.5 runtime - environmental, zero regression); live canaries succeeded on gemini (native), grok (native), zhipu (opencode_go). Deterministic gates all pass incl. consistency, export safety, secret scan, both suites (177+368), evidence rehearsal. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
The workspace workflow/verification fixes (#2851) advanced main, so the 78aefe2f build's evidence was no longer exact-current for the Intel leg. Rebuilt, signed, notarized from 61348ead (9/9 gates; notary 29123546; bundle e97fe388). Wire contract digest unchanged (4de687b8): no runtime-source change between the builds, only workflow + verifier files outside the bundle closure. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…e 3) Rebuilt after the Intel workflow interpreter fix (#2853). 9/9 gates; notary 92a5e02a; bundle 4f8f00bb; wire digest unchanged (4de687b8). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…e 4) Rebuilt after the smoke inner-protocol fix (#2855). 9/9 gates; notary 1b99bd35; bundle f61f5485; wire digest unchanged (4de687b8). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Runbook Phase A2 step 4 requires the signed x86_64 bundle to join the staged tree as a second artifacts entry, but the importer replaced the manifest wholesale — importing the Intel handoff would silently drop the arm64 artifact. --handoff is now repeatable (max two): each handoff is validated by the existing sealed loader unchanged; manifests must agree outside their artifact rows (backstop — the sealed decoder already pins channel/wire/versions per handoff); (platform, arch) rows must be disjoint; rows are unioned in deterministic order and the merged document is re-validated through the same strict decoder before the unchanged wholesale-replace transaction. Single-handoff behavior is byte-identical (exercised live re-importing the cycle-5 arm64 handoff). Also imports runtime 4.0.6 rebuilt at 48a17808 (SUPPORTED_HOSTS fix in closure; 9/9 gates; notary 9b3e981b; bundle 739a02fe). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ure 4.0.6 activation)
sumitake
added a commit
that referenced
this pull request
Aug 19, 2026
Mechanical release PR: compile pending fragments (runtime 4.0.6 dual-arch distribution from #122, the v6.1.0 skills content, and accumulated entries) into the generated CHANGELOG.md. Sole diff is the generated changelog.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Distributes the signed/notarized provider runtime 4.0.6 and cuts agent-collab v6.1.1 as the first tagged publication of the merged-but-untagged v6.1.0 skills. Staged, fully gated, and live-qualified before this PR was opened; the darwin-x86_64 second-architecture bundle follows onto this same branch via the ARM-gated Intel handoff (Phase A2) before merge.
Runtime 4.0.6 (source
48a17808, workspace-built, all nine evidence gates true; arm64 notary9b3e981b…, x86_64 notary9d72324b…)Routing hardening, lifecycle diagnostics decoupled from authority, pinned worktree sealing, failure-text salvage. Wire-contract disclosure: digest advances
ee98d75b…→4de687b8…— the advisory response is additively widened (completeness,salvaged_from, one newreasonenum); the 12-action set and every authority/artifact contract are unchanged. Carrier matrix: no carrier moved; Antigravity remains async-only.Version surfaces (moved together per the release checklist)
Client pin 4.0.6; schema consts (version + wire digests top-level and artifact record) — committed manifest validated against the schema with a 2020-12 validator, positive and three negative cases; plugin 6.1.1 (Claude + Codex); marketplace + 52 skills regenerated; pinned tests (3 files + importer fixtures); root README (summary/What's-new/expected-unit), plugin README, migration doc; release-shaped changelog fragment with licensing entry.
Staged qualification (before this PR)
ok: 12 actions, 54 ready candidates; the non-ready set (codexprotocol_capability_drift×4 +codex_readiness_unavailable×2) is byte-identical to the currently-installed 4.0.5 runtime's — environmental, zero regression.okwith succeeded receipts: gemini (native), grok (native), zhipu (opencode_go).git diff --check, and the archive→evidence→checksum→SPDX rehearsal (39 bundle members co-packaged).Intel (darwin-x86_64) second-architecture leg — landed in
da42099Built by the ARM-gated Intel CI pipeline from the SAME source commit
48a17808; unsigned handoff promoted locally (signed + notarized, team 36UFP9KY4T, all nine gates true, notary9d72324b…). Qualification executed: native x86_64 readiness smoke on the Intel CI runner (pre-promote), then locally under Rosetta — direct readinessok(12 actions), full-stack staged carrier canary through the coordinator underarch -x86_64(grok, exact token, succeeded receipt), positive client resolution of theruntime/darwin-x86_64artifact (digest406c7668…= promote-released sha), and an arm64 native-resolution regression check. Manifest now carries exactly two per-architecture artifacts validating against the committed schema; the stale single-artifact test updated to assert the dual-arch activation.Compliance trace
author: claude
standing_directives: operator release authorization (2026-08-19, in-session); provider-runtime release runbook Phases B/B'; version-surface checklist; reliable/simple/elegant baseline
tier: 2
cross_check: PROCEED (round 1 of 1) — verbatim "VERDICT: PROCEED", no concerns, on the final dual-arch head da42099 (receipt request_sha256 f95485233939cad9…); earlier workspace-side receipts 7bd868fb…, c2e19818… cover the runtime content and version-identity decisions
post_condition: SATISFIED — the Intel (darwin-x86_64) bundle landed on this branch in da42099 with executed qualification; v6.1.1 ships both architectures
mcp_coverage_gap: NONE
plugin_affected: THIS IS the plugin distribution PR
readme_refresh_status: README updated (root ×3 spots, plugin, migration doc)
contributor_rights: OWNER-AUTHORED
operator_reserved: no