# Sprint 207 Plan: Projection Constraint Contract I

## Context
Projection/environment constraints are currently under-modeled in benchmark/execution flow.

## Goals
1. Introduce projection constraint schema in benchmark catalog tooling
2. Parse and persist target constraints through run packets
3. Emit missing-constraint diagnostics

## Steps

### Step 2074: Projection schema extension for run catalogs (10 tests)
Add fields for `core_semantics`, `projection_targets`, `resource_budgets`, `forbidden_apis`.

### Step 2075: Benchmark ingestion support for projection schema (10 tests)
Ingest and preserve projection metadata in result packets.

### Step 2076: Constraint completeness diagnostics (8 tests)
Emit deterministic errors on missing required projection contract fields.

### Step 2077: Projection metadata summary export (8 tests)
Expose projection contract status in benchmark summaries.

### Step 2078: Sprint 207 Integration Summary (8 tests)
Add `editor/src/Sprint207IntegrationSummary.h`.

## Architecture Gate
- Projection constraints must be first-class data, not dropped free-text.