whetstone_DSL/sprint184_plan.md

Sprint 184 Plan: Generator Capability Gap Detection and Routing

Context

We now have strict contract telemetry, but we still need explicit detection when the task is well-constrained and the failure is instead generator/runtime capability.

Goals

1. Add capability-signal inputs to queue and validation flows
2. Emit deterministic generator_capability_gap blocker/issue classification
3. Route capability gaps to debug/toolchain remediation tools

Steps

Step 1959: Queue capability-signal handling (10 tests)

Add capabilitySignals input to whetstone_queue_ready and emit:

• blocker generator_capability_gap when compile/test/toolchain failures are signaled
• deterministic blocker metadata + recommended tool list

Step 1960: Validation capability-signal scoring/classification (10 tests)

Add per-task capability_signals handling in whetstone_validate_taskitem:

• issue tagging for capability failures
• deterministic generator_capability_gap classification

Step 1961: Pipeline support for injected capability signals (8 tests)

Allow strict sprint pipeline to pass shared capability signal packets into queue and validation stages.

Step 1962: Remediation routing hint updates (8 tests)

Ensure dominant gap class and next_action route capability gaps toward debug/toolchain remediation paths.

Step 1963: Sprint 184 Integration Summary (8 tests)

Add editor/src/Sprint184IntegrationSummary.h.

Architecture Gate

• Well-constrained tasks with compile/test/toolchain failures must classify as generator_capability_gap, not under_constrained_taskitem.