whetstone_DSL/sprint125_plan.md

Sprint 125 Plan: Batch Debug Automation and Safety Envelopes

Context

Sprints 121-124 established deterministic debug artifacts and guarded patch execution. Sprint 125 scales this into batch workflows with safety envelopes, prioritization, and deterministic campaign reports suitable for SLM fleets.

---

Goals

1. Add batch campaign models for multi-target debugging
2. Add safety envelope policies for stop/continue decisions
3. Add MCP tools to run, monitor, and summarize debug campaigns
4. Keep deterministic output and reproducible ordering throughout

---

Steps

Step 1489: Debug campaign spec model (12 tests)

Step 1490: Campaign target prioritizer (10 tests)

Step 1491: Safety envelope policy model (10 tests)

Step 1492: Campaign progress tracker model (8 tests)

Step 1493: whetstone_start_debug_campaign MCP tool (8 tests)

Step 1494: whetstone_step_debug_campaign MCP tool (8 tests)

Step 1495: whetstone_get_debug_campaign_status MCP tool (8 tests)

Step 1496: whetstone_stop_debug_campaign MCP tool (8 tests)

Step 1497: Campaign report bundle generator (8 tests)

Step 1498: Sprint 125 integration summary + regression (8 tests)

---

Architecture Gate

• Campaign decisions must remain deterministic
• Safety envelope violations must halt campaign immediately
• Campaign status is fully machine-readable and replayable
• Max 600 lines per header