Tags: alexadark/riff

feat(next-step-5c): surface smoke failures via AskUserQuestion triage

Step 5c now branches DROPPED into three buckets:
1. Task drops (existing behavior, unmatched_tasks)
2. Smoke section too thin or missing (smoke_too_thin, empty planned_smokes
   on non-legacy plans) → ask the planner to expand
3. Smoke regressions or missing results (failed_smokes, unmatched_smokes)
   → auto-debug | fix manually | skip

schema_version accepts both 1 (legacy pre-Smoke plans) and 2 (current).

Companion to 6f1bd20 (smoke contract). Without this, smoke failures
would only block at the executor (no SUMMARY) but never surface to
the user via the orchestrator — now they do.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>