# Sprint 127 Plan: Deterministic Debug Assist Packets

## Context

Sprint 126 added checkpointing/resume/export for campaigns. Sprint 127 focuses on
making debugging guidance more explicit and machine-friendly so smaller agents can
follow constrained steps reliably.

---

## Goals

1. Add deterministic hint and triage models
2. Add bounded repro reduction and patch risk labeling models
3. Add MCP tools for hinting/triage/repro/risk
4. Preserve deterministic outputs and machine-readable packets

---

## Steps

### Step 1509: Debug hint template model (10 tests)
### Step 1510: Failure triage score model (10 tests)
### Step 1511: Minimal repro reducer model (8 tests)
### Step 1512: Patch risk labeler model (8 tests)
### Step 1513: `whetstone_generate_debug_hints` MCP tool (8 tests)
### Step 1514: `whetstone_score_failure_triage` MCP tool (8 tests)
### Step 1515: `whetstone_reduce_repro_command` MCP tool (8 tests)
### Step 1516: `whetstone_label_patch_risk` MCP tool (8 tests)
### Step 1517: Debug assist packet bundle model (8 tests)
### Step 1518: Sprint 127 integration summary + regression (8 tests)

---

## Architecture Gate

- Hints and scores must be deterministic for identical inputs
- Repro reduction must be bounded and machine-readable
- Risk labels must include explicit rationale and level
- Max 600 lines per header