claw/docs/superpowers/specs/2026-04-21-generated-scene-local-doc-pipeline-residual-closure-design.md

Generated Scene Local-Doc Pipeline Residual Closure Design

Date: 2026-04-21

Parent status source:

• docs/superpowers/reports/2026-04-21-generated-scene-runtime-semantics-validation-refresh-execution-report.md

Problem Statement

After runtime-semantics hardening, rematerialization rerun, and validation refresh rerun, the remaining unresolved generated-scene residuals are narrowed to 6 local_doc_pipeline scenes:

1. sweep-025-scene
2. sweep-047-scene
3. sweep-050-scene
4. sweep-052-scene
5. sweep-062-scene
6. sweep-087-scene

All six currently fail-closed during generation because workflow evidence is still considered incomplete for archetype local_doc_pipeline.

Goal

Create a bounded route that inspects only these six residual scenes, identifies the missing reusable workflow-evidence patterns, and closes them at generator/analyzer rule level so that the next rematerialization rerun can reduce or eliminate the remaining local_doc_pipeline failures.

Source-First Principle

This route remains source-first:

1. inspect the six original source scene directories
2. identify reusable evidence shapes that should count as valid local_doc_pipeline workflow evidence
3. encode only reusable evidence recovery, not one-off generated-output patching

Closure Target

The route succeeds if it publishes a reusable first slice that makes the missing workflow evidence recognizable for the bounded six-scene bucket.

The route does not itself claim final closure of all six scenes; final closure is proven only after downstream rematerialization rerun and validation refresh rerun.

Expected Reusable Focus

The likely reusable closure surface is one or more of:

1. doc-export evidence variants not currently recognized
2. local report-log / staging-file workflow shapes not currently recognized
3. query-leg + doc-export combinations that should count as local_doc_pipeline
4. evidence recovery from source-side helper scripts or embedded config files

Outputs

This design leads to a bounded implementation plan that:

1. fixes only generator/analyzer rule recovery for the six-scene bucket
2. publishes route-local followup JSON
3. publishes route-local report
4. does not rerun rematerialization or validation refresh inside the route