# Sprint 182 Plan: Capability Gap Telemetry and Auto-Remediation Hints

## Context
When strict contracts fail, we need deterministic telemetry about whether the
problem is under-constrained taskitems or insufficient codegen capability.

## Goals
1. Emit structured gap telemetry for strict contract failures
2. Attach recommended tools/remediation metadata to blockers
3. Produce batch summary artifacts for sprint-level triage

## Steps

### Step 1949: Strict-gap reason packet schema (10 tests)
Define deterministic packet fields:
- `gap_class`
- `missing_fields`
- `likely_root_cause`
- `recommended_tools`

### Step 1950: Queue+validation metadata enrichment (10 tests)
Attach gap packets to queue blockers and validation issues.

### Step 1951: Sprint pipeline summary enrichment (8 tests)
Emit strict-gap aggregate counts and top remediation tool recommendations.

### Step 1952: Regression fixtures for under-constrained vs capability-limited cases (8 tests)
Add deterministic fixtures that separate:
- missing contract metadata
- codegen/toolchain inability

### Step 1953: Sprint 182 Integration Summary (8 tests)
Add `editor/src/Sprint182IntegrationSummary.h`.

## Architecture Gate
- Every strict blocker must carry deterministic remediation metadata.