v0.1.0.dev5

Changes

This prerelease fixes admission of otherwise valid AGY review results that include provider-generated toolAction or toolSummary metadata. It implements the shared C80 / R-AGY-METADATA contract and consolidates the PR #20/#22 adoption and release documentation in PR #24.

• Adds the public separate_agy_metadata(raw, *, declared_fields=()) helper. It strictly parses original JSON first, then separates only undeclared top-level toolAction and toolSummary fields. It returns payload and metadata dictionaries without changing the raw input.
• Applies that separation automatically in admit_output for the agy-stream-json carrier. Declared fields, nested fields and other unknown fields remain subject to the existing contract.
• Preserves duplicate-key, encoding and non-finite-number rejection; terminal failure checks; canonical schema validation; all six invocation bindings; and negative review verdicts. Generic validate_verdict, native-final and other carriers remain strict.
• Clarifies C23 recovery: retain original AGY bytes and separated metadata, project the payload when needed, and pass the projected JSON through strict native-final validation.
• Documents independent Codex, Claude and AGY host adoption, manual release notice delivery and the existing automation limits.

Consumer action

The README and dated status documents in this frozen source were written before publication and still call dev5 an unpublished candidate. This release and its completed artifact manifest supersede that publication-status wording; the retained wording has no runtime effect.

Pin this exact release and verify the wheel/sdist against the triad-release.json manifest attached by the release workflow. Hosts adopting the helper directly must preserve raw output and metadata, and retain their terminal, schema and invocation-binding checks. Existing host-specific adapters, model/effort selection, installation and configuration remain host-owned.

This library release does not approve or deploy Codex adapter PR #47, upgrade an installed toolkit, or establish fresh installed-session behavior. Each consumer must complete its own integration, native verification and review. The two-host automated notice workflow is separate from the owner-requested manual notices to all three consumers; no GitHub App configuration is changed by this release.

Compatibility and verification

• Additive API; existing dev4 public API floor and canonical schema identities are retained.
• Python 3.12 or later, as before. This is a development prerelease, not a stable release.
• Reviewed PR #24 candidate: 30bf2c93d712ea6adbecb54adb7516d6ce017246.
• Merge source: 859f27c07c1123e87b50344f587999a0cbc172a6; its complete file tree is identical to the reviewed candidate.
• Final review round 20261023-lib24-release-r2-b73603: Opus, Sol and Argon all SAFE TO MERGE, collection AGREED, final ROUND_INTEGRITY_OK; separate Astra comparison found no actionable defect.
• Candidate validation: 1,397 local tests, specification assets and authoring map, API compatibility, sdist-to-wheel rebuild and installed-wheel verification; exact-head native Ubuntu/macOS CI passed.
• Published archives are supplied only by the exact-tag release workflow after its four native source/archive/wheel verification jobs pass. The attached manifest records the final source commit and artifact identities.

PR: #24

Full comparison: v0.1.0.dev4...v0.1.0.dev5