Skip to content

runtime: ship provider runtime 5.0.2 in agent-collab 7.0.1 - #188

Open
sumitake wants to merge 1 commit into
mainfrom
dev/codex/runtime-5.0.2-release
Open

runtime: ship provider runtime 5.0.2 in agent-collab 7.0.1#188
sumitake wants to merge 1 commit into
mainfrom
dev/codex/runtime-5.0.2-release

Conversation

@sumitake

@sumitake sumitake commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Summary

Ship agent-collab 7.0.1 with the paired signed and notarized provider runtime 5.0.2 for macOS arm64 and x86_64. The release advances the public client and wire descriptor to schema 9, restores durable Grok managed-route parity, preserves source-seal failure fidelity, and makes admitted repository actions use descriptor-owned inactivity liveness.

Result admission remains semantic and tolerant: provider prose, formatting, passive metadata, previously unseen fingerprints, and unknown ACP metadata do not veto a contract-valid artifact grounded in sealed source evidence. Provider-started failures remain terminal and are never automatically replayed.

Boundary declaration

  • No provider executor source, raw provider command, credential, private absolute path, retired package tree, downloader, or post-install hook is included.
  • Native-runtime changes contain only final signed/notarized artifacts and reviewed public verification metadata; implementation and credentials remain private.
  • The change does not create a host-specific preset or provider-specific plugin.

Generated and release surfaces

  • Skill specs and generated SKILL.md files are in parity.
  • Claude and Codex marketplaces/manifests are in parity.
  • A unique 7.0.1 changelog fragment is present and the activation-release CHANGELOG.md is deterministically compiled from all pending fragments.
  • All seven public version surfaces advance together to 7.0.1.
  • The public runtime manifest binds runtime 5.0.2, wire schema 9, and both notarized architecture bundles as one release unit.

Verification

Exact signed head: cb04cdbce23a92f2b93520ac36d9f75049c70c5a.

  • python3 scripts/build_skills.py --check
  • python3 scripts/build_marketplace.py --check
  • python3 scripts/build-changelog.py --check
  • python3 -m unittest discover -s tests -p 'test_*.py' -v — 308 passed
  • python3 -m unittest discover -s scripts -p 'test_*.py' -v — 456 passed
  • python3 scripts/check_release_consistency.py
  • python3 scripts/validate_runtime_manifest_schema.py
  • python3 scripts/verify_project_estimation_maintenance.py --expected-version 7.0.1
  • python3 scripts/secret_scan.py — 496 source text files, clean
  • python3 scripts/check-public-export-safety.py --active-tree --history
  • git diff --check origin/main...HEAD
  • Native GPG verification and GitHub signature verification both report the exact head valid.

No semantic provider call was used for these deterministic release gates.

Review and post-condition

Tier 3 because this changes signed runtime verification, routing/liveness behavior, and the release supply chain. The single exact-head Gemini governance attempt ended source_containment_failed / absolute_outside_roots after one provider process and produced no artifact or receipt; cleanup was confirmed and the attempt was not replayed or failed over. A valid independent review remains pending. After normal merge, create the signed annotated v7.0.1 tag through the governed release path, verify all published assets, install and activate once, restart once, read back immutable installed bytes/runtime identity, and then complete the separately governed documentation closeout.

author: Codex
standing_directives: Public source boundary, exact-head Tier-3 governance, signed commits, provider-free release validation, no semantic replay, normal merge, and immutable post-release readback followed
tier: 3
cross_check: AWAITING OPERATOR-AUTHORIZED ALTERNATIVE — exact-head Gemini governance at cb04cdb ended source_containment_failed after provider start; no receipt; not replayed
post_condition: Signed v7.0.1 tag and assets verified; install/activate and one restart; immutable installed-byte/runtime readback; final documentation closeout
mcp_coverage_gap: NONE
contributor_rights: OWNER-AUTHORED
operator_reserved: no

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for security reviews. Please try again later.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

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

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T04:18:03.194961Z cb04cdb 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.

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ba65afa-5221-4367-849c-52587818c205


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cb04cdbce2

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

Comment thread CHANGELOG.md
the fix takes effect once the primary checkout (whose working tree hosts
the active hooksPath copies) is updated to a commit containing it.

- Ship the paired signed provider runtime 5.0.2 generation with source-seal

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Drop the generated CHANGELOG changes from this commit

This commit adds the 7.0.1 fragment to CHANGELOG.md even though repository policy requires user-visible changes to commit only their unique changelog.d/ fragment and leaves compilation of this generated file to the release flow. Remove the CHANGELOG.md diff and retain changelog.d/2026-08-30-001-runtime-5.0.2.md.

AGENTS.md reference: AGENTS.md:L41-L42

Useful? React with 👍 / 👎.

Comment thread README.md
fixes together under wire digest
`86137024f7e16c67bbeb9f29eaee03d8031e645ce1b5b2c46154aeae7528bcd9`.

## What's new - v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the v7.0.0 release notes labeled v7.0.0

The newly added unreleased section already describes v7.0.1/runtime 5.0.2, while the section under this renamed heading is unchanged v7.0.0 material and explicitly describes the published runtime 5.0.0 and wire schema 8. Readers now see two v7.0.1 sections with contradictory runtime identities; restore this heading to v7.0.0 and update the consistency check to recognize the separate unreleased-source heading instead.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant