[bokelley]

Summary

next already adopts the signed 3.3.0-beta.3 bundle (#1754) and stamps status on list_products / decline_proposals from that release on. That gate compares version strings. This PR makes the served release's own response schema decide, which is the contract in the task (and adcp-client#3493 for the TypeScript SDK), and closes three defects the string comparison leaves for a 3.2.x peer. Each is reproduced by a test that fails on next today.

Defect on next	Fix
A typed ListProductsResponse dumps its defaulted status: completed; a server serving 3.2.x sends it to a closed root that forbids it (strict response validation fails).	_normalize_response_envelope drops only that implied completed where the served release has no status for the tool. A submitted arm keeps its status.
3.3 → 3.2 conversion of a synchronous decline_proposals response raises ADCPVersionConversionError (the 3.2 root permits status only as submitted).	New _convert_compact_status drops completed going down, as a recorded ConversionLoss.
3.2 → 3.3 conversion does not supply the status 3.3 requires.	The same rule supplies completed going up.
A 3.2.x release that composes the envelope (the backport) is still treated as one that does not.	uses_task_status_envelope(tool, version) asks the release's schema (response_composes_protocol_envelope: does a root allOf arm require status / reference protocol-envelope?). The #1754 version comparison stays as the answer for a release that ships no schema for the tool.

Nothing is stripped for any other tool or release. tests/test_response_status_gating.py includes a test that serves the composed schema as 3.2's and checks the answer flips with no code change.

Context

This supersedes #1760, which adopted the same bundle in parallel. I opened it before #1754 landed; on rebase everything except the items above was already on next (including the controller task_id bound and the compact-response gating), so I closed it.

Test plan

• pytest tests: 20,880 passed, 0 failed, 2,833 skipped, 1 xfailed
• make typecheck and ruff check src/ packages/adcp-reporting-storage/src
• 27 new tests in tests/test_response_status_gating.py; 4 fail on next without this change

🤖 Generated with Claude Code

[aao-secretariat]

Ladon verdict: Approve

Approve — compact-response status gating now reads the served release's own response schema (response_composes_protocol_envelope → root allOf composing core/protocol-envelope.json) rather than a brittle version-string compare, fixing three defects for a 3.2.x peer plus the backport case.

What I checked:

• Scope: Logic is tightly scoped to the two native-compact tools (list_products, decline_proposals); the version-string path survives as a fallback for releases without a schema.
• Minor-release pathway (DR-0032/DR-0033): The schema-driven gating is a Moves-style translation handled in both directions, with coverage.
• Semver signal: fix(compat): is correct — no public-surface removal, rename, type-signature change, or required↔optional flip; buyers/sellers continue to deserialize.
• Tests: 27 new tests cover both conversion directions, the server-strip path, and the schema-flip case.
• High-risk flag: True only because src/adcp/compat/** and src/adcp/server/** were modified; both are presumed safe with no medium-or-higher findings.

No Critical/High/Medium findings. No gated paths, no no-auto-approve team match, no prior decision. Falls through to row 9.