# Sprint 185 Plan: Executable Capability-Gap Handoff to Debug Loop

## Context
Sprint 184 classifies `generator_capability_gap`, but current output is still
advisory. We need a deterministic, executable call plan for immediate handoff.

## Goals
1. Emit a concrete debug-loop tool call plan when capability gaps are detected
2. Include stable argument skeletons and call ordering
3. Surface plan in queue, validation, and pipeline summary artifacts

## Steps

### Step 1964: Queue remediation call-plan emission (10 tests)
When dominant gap is `generator_capability_gap`, emit `debugLoopCallPlan`:
- ordered tool list
- deterministic argument stubs
- stop conditions

### Step 1965: Validation remediation call-plan emission (10 tests)
Emit report-level `capability_gap_call_plan` when any task is classified as
`generator_capability_gap`.

### Step 1966: Pipeline summary propagation of call plan (8 tests)
Include queue/validation call plan metadata in `00_summary.json`.

### Step 1967: Deterministic plan fingerprinting (8 tests)
Add stable `plan_fingerprint` for routing reproducibility.

### Step 1968: Sprint 185 Integration Summary (8 tests)
Add `editor/src/Sprint185IntegrationSummary.h`.

## Architecture Gate
- Capability-gap output must include a directly runnable, deterministic call
  sequence for debug-loop execution.