runtime: ship v6.0.6 hardened ACP carriers on runtime 4.0.5 - #116
Conversation
Import the sealed provider runtime 4.0.5 (workspace b142f521): repairs the 4.0.4 readiness crash behind the v6.0.5 rollback (route-local probe containment with exception-class diagnostics), tolerates ACP display-title drift (kind-primary evidence with quoted-span-aware deny scan; strict authorization unchanged), resolves role-tagless OpenCode catalogs through a deterministic newest-dominant ladder, and makes failure envelopes fail-safe. Public client: dedicated bounded teardown budget and success-preserving cleanup (ends the frequent false agy teardown_error), intent-check at standard/standard on the verify intent. Package 6.0.6 across all version surfaces; staged qualification passed pre-merge (readiness full-ok; Grok ACP and OpenCode ACP canaries receipted PASS). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jq8DbD7NH7fth58kKdYVGx
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4ac150b69f
ℹ️ 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".
| process, | ||
| deadline=time.monotonic() + TEARDOWN_REAP_SECONDS, | ||
| ): | ||
| teardown_note = "process group teardown unproven" |
There was a problem hiding this comment.
When process-group teardown is unproven after a clean exit, this note is only attached to RuntimeResult.error for ok results; the advisory and failure constructors omit it, and the normal coordinator path treats ok/advisory as usable and deliberately does not serialize result.error (coordinator.py:307-319). Consequently, callers receive an indistinguishable usable response even though a descendant may remain alive, so the cleanup failure is not actually “recorded” and conflicts with the documented fail-typed cleanup behavior in docs/architecture/lifecycle-and-operations.md:180-183. Preserve the note in serialized provenance/diagnostics for every valid response, or retain a typed teardown failure.
Useful? React with 👍 / 👎.
1 participant
Summary
Ships provider runtime 4.0.5 (workspace
b142f521) — repairing the readiness crash behind the v6.0.5 rollback and hardening every brittleness found this cycle — plus the public-client teardown tolerance and the standard-effort intent-check. Package 6.0.6 across all version surfaces.Runtime bundle SHA-256:
e4904cd75794eba75c709c1a9d0061324964164d1e0ced59dda3e3335ab15005Notarization:
bf8137c1-cd0c-47d9-aed4-93fc91d3bd51(team36UFP9KY4T, hardened runtime, secure timestamp)Staged qualification (pre-merge, on these exact staged bytes): readiness
okfull snapshot (codex candidates route-locally degraded, zhipu 9/9 ready); Grok ACP canary receipted PASS; OpenCode ACP canary receipted PASS (GLM-5.3 via the newest-dominant ladder).Change inventory: sealed 4.0.5 import (importer byte-binding); client
PROVIDER_RUNTIME_VERSION4.0.4→4.0.5; dedicated bounded teardown budget + success-preserving cleanup (ends the false agyteardown_error); schema consts release-exact (4.0.5 + wireee98d75b…); intent-check at standard/standard (operator-adjudicated verify-intent floors); READMEs/marketplace/migration-doc/fragment; version-pinned tests updated; the consumed mis-fit review-action canary and its advisory are recorded in the session log (runbook note: opencode carrier canaries use text-artifact actions).Compliance trace
author: claude
standing_directives: qualify-before-publish runbook ordering, operational-reliability baseline, fragment-only changelog followed
tier: 3
cross_check: PROCEED — Gemini via the staged qualified 4.0.5 coordinator at exact head 4ac150b, verbatim "VERDICT: PROCEED / CONFIDENCE: H / CONCERNS: (none)"; receipt governance_verdict APPROVE, artifact_sha256 b8eed0fc6c8d3d808de13b9221eb204417d1990b509d02a3e1a0a59881268772
peer_review_verdict: BLOCKED — managed reviewer unavailable: Grok governance x4 typed failures (1 receipt-less advisory on the broken installed runtime; then on the staged fixed runtime: one invalid_final after 63 bound reads, two pre-provider flakes); Codex schema-drifted (temporarily_unavailable) on this host; GLM not governance-admitted (invalid_request). Fewer than 2 admissible distinct-family reviewers — routed to operator per the failover contract.
post_condition: operator merge decision → mechanical changelog PR → immutable v6.0.6 tag/assets cut last → activation on all four primary hosts with per-host rollback prepared
mcp_coverage_gap: NONE
operator_reserved: pending operator adjudication of the peer leg
contributor_rights: OWNER-AUTHORED