# Sprint 181 Plan: Queue and Validation Contract Enforcement

## Context
Generation metadata is only useful if queue readiness and validation enforce it.

## Goals
1. Enforce strict execution contracts in `whetstone_queue_ready`
2. Add execution-specificity scoring to `whetstone_validate_taskitem`
3. Surface explicit blocker classes for missing contract fields

## Steps

### Step 1944: Strict queue gate for execution contracts (10 tests)
In strict mode, queue blocks on:
- missing `executionContract`
- missing required contract fields
- low `executionSpecificityScore`

### Step 1945: Validation scoring extension (10 tests)
Add:
- `execution_specificity_score` per task
- `average_execution_specificity_score` in report
- strict-mode deductions for weak contract metadata

### Step 1946: Pipeline propagation for strict contract flags (8 tests)
Ensure sprint pipeline passes strict flags and contract payloads from generate
to queue and validator stages.

### Step 1947: Deterministic blocker taxonomy (8 tests)
Guarantee stable blocker labels:
- `missing_execution_contract`
- `execution_specificity_low`
- existing blockers

### Step 1948: Sprint 181 Integration Summary (8 tests)
Add `editor/src/Sprint181IntegrationSummary.h`.

## Architecture Gate
- Ready state must reflect contract quality, not just structural task presence.