Description
The resolve_pull_request_review_thread safe-outputs handler hard-fails when supplied a PullRequestReviewComment node ID (PRRC_...) instead of the required PullRequestReviewThread node ID (PRRT_...). Confirmed in the PR Sous Chef run §30838483274: 2 of 13 items in the batch failed with thread_id must reference a PullRequestReviewThread node ID (PRRT_...); received PullRequestReviewComment for PRRC_kwDOPc1QR87c6owv. This is deterministic and mappable (a comment always has exactly one parent thread), so the failure is preventable rather than a genuine ambiguity.
Expected Impact
Eliminates a recurring class of item-level safe-output validation failures that currently mark otherwise-successful batches (9/13 and similar) as job failures, and removes an easy trap for agents constructing thread-resolution calls from comment IDs.
Suggested Agent
Existing maintainer of the safe-outputs handler for resolve_pull_request_review_thread (pkg/workflow safe-outputs implementation)
Estimated Effort
Medium (1-4 hours) — either clarify the tool schema/description to state the required node-ID type explicitly, or add a server-side PRRC→PRRT resolution fallback via the reviewThreads GraphQL connection so a comment ID self-heals instead of hard-failing.
Data Source
DeepReport Intelligence Briefing 2026-08-04, cross-referencing Safe Output Health Monitor discussion (2026-08-04 audit, Cluster 1).
Generated by 🔬 Deep Report · agent · 197.5 AIC · ⌖ 40.2 AIC · ⊞ 11K · ◷
Description
The
resolve_pull_request_review_threadsafe-outputs handler hard-fails when supplied a PullRequestReviewComment node ID (PRRC_...) instead of the required PullRequestReviewThread node ID (PRRT_...). Confirmed in the PR Sous Chef run §30838483274: 2 of 13 items in the batch failed withthread_id must reference a PullRequestReviewThread node ID (PRRT_...); received PullRequestReviewComment for PRRC_kwDOPc1QR87c6owv. This is deterministic and mappable (a comment always has exactly one parent thread), so the failure is preventable rather than a genuine ambiguity.Expected Impact
Eliminates a recurring class of item-level safe-output validation failures that currently mark otherwise-successful batches (9/13 and similar) as job failures, and removes an easy trap for agents constructing thread-resolution calls from comment IDs.
Suggested Agent
Existing maintainer of the safe-outputs handler for
resolve_pull_request_review_thread(pkg/workflow safe-outputs implementation)Estimated Effort
Medium (1-4 hours) — either clarify the tool schema/description to state the required node-ID type explicitly, or add a server-side PRRC→PRRT resolution fallback via the
reviewThreadsGraphQL connection so a comment ID self-heals instead of hard-failing.Data Source
DeepReport Intelligence Briefing 2026-08-04, cross-referencing Safe Output Health Monitor discussion (2026-08-04 audit, Cluster 1).