whetstone_DSL/sprint128_plan.md

Sprint 128 Plan: Deterministic Debug Recipes and Trace Capture

Context

Sprint 127 introduced assist packets for smaller agents. Sprint 128 adds explicit recipe retrieval, action validation, and trace capture so low-capability agents can execute bounded debug procedures with auditable history.

---

Goals

1. Add deterministic recipe and validation models
2. Add deterministic execution trace models
3. Add MCP tools for recipe retrieval/validation/trace record/query
4. Keep outputs machine-readable and replay-stable

---

Steps

Step 1519: Debug recipe step model (10 tests)

Step 1520: Debug recipe library model (10 tests)

Step 1521: Debug action validator model (8 tests)

Step 1522: Debug execution trace model (8 tests)

Step 1523: whetstone_get_debug_recipe MCP tool (8 tests)

Step 1524: whetstone_validate_debug_action MCP tool (8 tests)

Step 1525: whetstone_record_debug_trace MCP tool (8 tests)

Step 1526: whetstone_get_debug_trace MCP tool (8 tests)

Step 1527: Debug recipe packet model (8 tests)

Step 1528: Sprint 128 integration summary + regression (8 tests)

---

Architecture Gate

• Recipe lookup must be deterministic by failure class
• Action validation must return explicit rule violations
• Trace records must preserve order and be machine-readable
• Max 600 lines per header