whetstone_DSL/sprint145_plan.md

Sprint 145 Plan: C++ Constructive Editor Fast Path and Toolchain Integration

Context

To unlock immediate value, hybrid mode must feel native for C++ teams. Sprint 145 optimizes the C++ constructive fast path end-to-end.

---

Goals

1. Optimize C++ edit->sync->build->feedback loop latency
2. Integrate compile/test diagnostics directly into hybrid editing flow
3. Prioritize battle-tested C++ paths while AST-native language work continues
4. Provide one-call C++ constructive loop orchestration

---

Steps

Step 1689: C++ constructive loop state model (10 tests)

Step 1690: Incremental compile feedback packet model (10 tests)

Step 1691: C++ test-feedback bridge model (10 tests)

Step 1692: C++ loop latency budget enforcer model (10 tests)

Step 1693: whetstone_run_cpp_constructive_step MCP tool (8 tests)

Step 1694: whetstone_get_cpp_constructive_status MCP tool (8 tests)

Step 1695: whetstone_run_cpp_constructive_loop MCP tool (8 tests)

Step 1696: C++ constructive readiness scorer model (8 tests)

Step 1697: C++ constructive loop report artifact (8 tests)

Step 1698: Sprint 145 integration summary + regression (8 tests)

---

Architecture Gate

• C++ loop behavior must be deterministic and bounded
• Feedback packets must be structured and machine-readable
• One-call loop tool must expose explicit stop reasons
• Max 600 lines per header