[Bug] Agent stuck in infinite retry loop on StructuredOutput schema validation

Bug Description
Agent got stuck in a retry loop and burned through entire 5 hour token session in a short amiunt of time. My chat:

⏺ That agent is stuck in a runaway retry loop — it's the pass-2b partd-retry-suppress adjudicator, and here's exactly what it's doing: - Its real work finished fine: 16 Read + 11 Bash = it traced the Part-D retry state machine and the worker succeededSources push sites, same as my own first-hand check. - Then it jammed on output: 395 StructuredOutput attempts, every single one bounced with "Output does not match required schema: must have required property 'finding_id'…". It's been spinning on that one schema-validation failure for ~30 min, unable to emit, even narrating "I have attempted the StructuredOutput call over a hundred times…". That's the "lots of tool calls" you saw — ~844 events, 1.6 MB, almost all wasted retries. The other pass-2b agent (family-blind reader) went quiet 30 min ago, also without emitting. It's producing nothing and burning tokens, so I'll kill it. It does not affect the review — I already settled both of its targets first-hand (read the search_course_chunks body for the family-blind reader → RD-1/P1; read the push sites + retry state machine → KEY-1/DEL-R/P2), and both are in the finished report. ⏺ Stop Task It's producing nothing and burning tokens, so I'll kill it. It does not affect the review — I already settled both of its targets first-hand (read the search_course_chunks body for the family-blind reader → RD-1/P1; read the push sites + retry state machine → KEY-1/DEL-R/P2), and both are in the finished report. ⏺ Stop Task ⎿  Re-run the 2 pass-2 agents that failed to emit structured output · stopped ⏺ Killed the stuck workflow. Summary of what that last agent was doing: it was the re-run adjudicator for the Part-D retry finding. It completed its actual code/SQL investigation early (the 16 reads + 11 bash calls), then got trapped in a 395-attempt StructuredOutput loop — every attempt rejected for a missing finding_id property it couldn't satisfy. Pure wasted spin, ~30+ minutes, now stopped.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.170
• Feedback ID: 8e5e48c7-1ed0-42a9-82ae-c5e4830a9af2

Errors

[]