# G3 Enrichment Request Closure Plan

> Date: 2026-04-19
> Status: Draft
> Parent Framework Plan: `docs/superpowers/plans/2026-04-19-scene-skill-102-full-coverage-framework-plan.md`
> Parent Route: `Route 2: G3 / paginated_enrichment`
> Parent Layer: `Layer C + Layer D`
> Upstream Design: `docs/superpowers/specs/2026-04-19-g3-enrichment-request-closure-design.md`

## Plan Intent

Implement the first bounded `G3` contract-recovery slice by recovering repeated enrichment-request and secondary-request evidence gaps inside the remaining `paginated_enrichment` fail-closed bucket.

## Fixed Input Bucket

`paginated_enrichment + g3_enrichment_contract + secondary_request`

## Allowed Files

1. `src/generated_scene/analyzer.rs`
2. `src/generated_scene/generator.rs`
3. `src/generated_scene/ir.rs`
4. `tests/scene_generator_test.rs`
5. route-local follow-up JSON and report assets

## Forbidden Files

1. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
2. Route 3+ plan files
3. family promotion assets

## Tasks

1. freeze the targeted `G3` subgroup from the current follow-up asset
2. confirm the repeated enrichment-request missing pattern
3. implement one bounded contract-recovery slice
4. rerun only the bounded validation needed by this subgroup
5. publish subgroup delta and residual subgroup count

## Expected Coverage Delta

1. reduce the count of `paginated_enrichment` fail-closed records caused primarily by enrichment-request closure failure
2. do not reduce canonical or real-sample `G3` pass stability

## Completion Criteria

1. targeted subgroup has a measured before/after count
2. remaining unresolved Route 2 issues are explicitly handed to the next child plan
3. no route drift into `host_bridge_workflow`

## Stop Statement

Stop after the targeted enrichment-request subgroup has been corrected or explicitly bounded as residual.

Do not continue into export-plan closure work under this plan.