Expose typed reasons for native output failures - #5520

Approved after coordinator and independent static review. Content-free integrity reasons follow the selected originating failure across native error propagation and Python conversion. Same-ID ambiguity stays unknown; ordinary provider metadata, retry behavior and tool-effect settlement remain intact. Reviewed HTTP/WebSocket, child ownership, delivery-order and already-running-effect coverage. Linux and Windows hosted snapshots passed; macOS and Rust CodeQL remain pending. No candidate code or local tests ran.

Static re-review of fe8029b56cc454f2fc7dafca24089549deab999f: approved. The child-question regression now waits for a successor snapshot within the existing deadline. The final rebase adopts the base worker test that captures the actual shell job directory, addressing the earlier TMPDIR assumption. Exact old/new tree comparison: 45 changed files, 44 identical to current base; the remaining API fixture preserves the integrity-reason additions while integrating the base fixture update. Hosted native CI remains pending; no candidate code or local tests run.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4e7cb7e722

Approved after static re-review. Saved-login integration preserves the reviewed integrity-reason behavior in overlapping source and API fixtures. Hosted CI/native builds remain pending. No candidate code or tests executed.

Approved after static review and independent review. The test-only update addresses existing feedback about fabricated enum values while preserving absent/null coverage. Runtime and native inputs are unchanged. Hosted CI remains pending; no candidate code or tests executed.

Approved the integration at d9da489. Child admission, tool callbacks and step selection retain the creation-owned tracing context, including explicit absence, without replacing an existing turn carrier. The original feature changes remain intact. The fixture changes correctly wait for child observation before release and accept either winner of competing manual replies while requiring exactly one success.

Static review with an independent reviewer; no candidate code or tests were run. Fresh hosted CI remains pending. The unchanged shared tracing patch does not clear the separately tracked base security finding.

Approved at 70eaa3c. The tracing security fix is incorporated unchanged while response-integrity reasons retain originating error metadata and completed effects. All four stack heads contain the exact reviewed W3C security patch from 5451026; the inherited tracing blocker is addressed here. Final ancestry commits do not change the reviewed trees.

Hosted checks: 19 SUCCESS, 4 IN_PROGRESS, 3 SKIPPED, 1 NEUTRAL. Coordinator and independent static review found no actionable integration regressions. No candidate code or local tests executed; no CI reruns requested.

Approved at 21f29bb. The sole incremental change drains buffered observations before cancelling a pending reader and asserts cancellation succeeds. The blocked policy, independent-reader assertions, privacy checks and enclosing timeout remain intact. No runtime changes.

Coordinator and independent static review found no actionable issues. Hosted CI: {'SUCCESS': 4, 'IN_PROGRESS': 4, 'NEUTRAL': 1}. CI follow-up remains open. No candidate code or local tests executed; no CI reruns requested.

Approved at df3969c. Re-reviewed the single-file incremental fix with an independent static review. It polls the existing release-command session instead of restarting the command, preserves accumulated output, and requires terminal exit 0. The ten-poll limit and existing 40-second timeout bound execution. Both fork-refusal/no-side-effect checks and saved-child linkage remain intact; runtime code is unchanged. No actionable findings.

This addresses the observed premature-completion test assumption in source. Fresh hosted runtime verification is still pending; the previous-head failure is not evidence that this commit has passed. No candidate code, local tests, or CI reruns were executed.