feat: add OpenResponses 2026-04-24 API support - #246
Conversation
|
Important Review skippedToo many files! This PR contains 489 files, which is 389 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (113)
📒 Files selected for processing (489)
You can disable this status message by setting the 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. Comment |
|
Addressed the five merge-blocking findings cross-checked from #245:
Verification: official OpenResponses compliance, make quality-checks, make parity-checks, and make test all pass locally. Commit: 9922b72. |
Derive an exact ExtensionRequirement for every canonical content-part extension (message and structured tool-result parts): ExtensionContentPart carries namespace/implementor, namespace derives deterministically from the prefixed wire type, and admission/routing/failover plus openresponsescompat self-admission require an exact declared extension with zero-network mismatch. OpenResponses decode/encode preserves the wire object losslessly and merges explicit divergent namespace/implementor metadata. Declare the exact item_reference item dialect in the generic OpenResponses backend defaults so the item_references capability is truthful, and flip the viable native OpenResponses matrix evidence/scenarios positive (row and column cells); general cells stay rejected before network.
|
Superseded by #250, which contains the same final implementation as one release-manifest-valid commit over main. This avoids historical per-commit repo-hygiene failures while retaining all review remediations. |
What changed
Security follow-up
QA follow-up
Verification
Platform note
Race verification remains unavailable on Windows because the local cgo/ThreadSanitizer toolchain cannot run it; stress, fuzz, leak, architecture, compliance, and full test gates pass.