You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[AW Top 10] 07 Make strict dry-run compile diagnostics reliable #72605
Strict dry-run compiles through the MCP server time out or fail on a deprecated key without actionable partial output.
Implementation scope
Return stage-specific partial results on timeout and surface per-workflow deprecation diagnostics, then remove the deprecated missing-tool declaration from the windows workflow.
Done when
A timed-out compile names the stage and returns partial per-workflow results.
The windows workflow passes the strict dry-run compile.
Why now
Two CLI exploration reports reproduce the problem on separate days, so one change addresses both.
No corroborating AW discussion; evidence comes from the source issues.
Unchanged AW sources close only after this summary is completed. Newer source activity and not-planned retirement do not trigger source closure. Assigned summaries are frozen; unassign to allow reclustering.
changed the title [-][AW Top 10] 09 Make strict dry-run compile diagnostics reliable[/-][+][AW Top 10] 07 Make strict dry-run compile diagnostics reliable[/+]on Oct 29, 2026
Activity
[-][AW Top 10] 09 Make strict dry-run compile diagnostics reliable[/-][+][AW Top 10] 07 Make strict dry-run compile diagnostics reliable[/+]