[deep-report] Fix Schema Consistency Checker max-turns escalation: 60-turn limit exceeded in 4/5 recent runs #30855

Summary

The Schema Consistency Checker workflow is exceeding its 60-turn maximum in 4 out of 5 recent scheduled runs, causing truncated analysis and incomplete outputs. This is a P1 escalating pattern that began around 2026-05-03 and is tracked in the aw-failures report.

Impact

• 4/5 recent runs truncated mid-analysis (incomplete schema consistency reports)
• Schema drift may go undetected when the checker terminates before completing
• Each failed run still consumes full token budget with no useful output

Root Cause Hypothesis

The schema consistency checker is likely analyzing an increasingly large or complex schema set without pagination/batching. As the schema count grows, each run requires more turns to complete, eventually hitting the 60-turn hard limit. Possible causes:

• Schema count has grown beyond the workflow's capacity (no batching)
• The workflow re-analyzes already-checked schemas on every run (no incremental state)
• A recent schema addition significantly increased analysis depth

Recommended Fix

1. Incremental analysis: Store which schemas were last checked (via cache/repo state) and only check new/modified schemas in each run
2. Batching: Split schema analysis into N-schema batches across multiple runs
3. Turn budget awareness: Add a check at turn 40 that saves partial results and calls noop with a summary rather than truncating
4. Schema count monitoring: Add a missing_data call if schema count exceeds a configurable threshold

Acceptance Criteria

• Schema Consistency Checker completes within 40 turns on 80%+ of runs
• No truncated outputs (all runs produce a complete conformance report)
• Run history: 5/5 success over the next week

References

• Failure report: #30795
• Failed run: §25479424655
• Source: DeepReport Intelligence Briefing 2026-05-07

AI generated by DeepReport · §25505251838

Generated by DeepReport - Intelligence Gathering Agent · ● 539.7K · ◷

• expires on May 9, 2026, 3:38 PM UTC