whetstone_DSL/sprint183_plan.md

Sprint 183 Plan: Constraint-vs-Capability Gap Telemetry

Context

Strict execution contracts are now enforced, but we still need deterministic telemetry that distinguishes under-constrained taskitems from codegen/runtime capability gaps.

Goals

1. Classify queue/validation blockers into deterministic gap classes
2. Attach recommended remediation tools per gap class
3. Emit sprint-level gap summaries for routing and triage

Steps

Step 1954: Queue blocker gap classifier (10 tests)

Add deterministic mapping from queue blockers to:

• under_constrained_taskitem
• generator_capability_gap
• environment_or_dependency_gap
• risk_or_ambiguity

Step 1955: Validation issue gap classifier (10 tests)

Classify validation issues using deterministic rules and include recommended_tools and next_action.

Step 1956: Pipeline summary gap aggregation (8 tests)

Aggregate:

• per-gap-class counts
• top recommended tools
• dominant root cause class

Step 1957: Routing hint packet for remediation loops (8 tests)

Emit deterministic remediationRoutingHints object suitable for debug/repair loops and future tool routing.

Step 1958: Sprint 183 Integration Summary (8 tests)

Add editor/src/Sprint183IntegrationSummary.h.

Architecture Gate

• Every non-ready outcome must include deterministic gap-class telemetry and actionable tool recommendations.