claw/docs/superpowers/specs/2026-04-21-generated-scene-runtime-semantics-validation-refresh-execution-design.md

Generated Scene Runtime Semantics Validation Refresh Execution Design

Date: 2026-04-21

Parent dependency plan:

• docs/superpowers/plans/2026-04-20-generated-scene-runtime-semantics-validation-refresh-plan.md

Parent rematerialization execution:

• docs/superpowers/plans/2026-04-21-generated-scene-runtime-semantics-rematerialization-execution-plan.md

Intent

Execute the full validation refresh required after the hardened runtime-semantics rematerialization.

Why A Child Execution Plan Is Required

The parent validation refresh plan is dependency-only and explicitly forbids executing validation refresh inside that plan. A separate execution plan is required to:

1. consume the refreshed canonical 102-skill bundle
2. regenerate validation-layer assets against the refreshed bundle
3. keep validation evidence separate from the old pre-hardening assets

Fixed Validation Layers

The execution must refresh these layers in order:

1. deterministic invocation readiness
2. natural-language parameter readiness
3. static validation
4. direct mock execution
5. pseudo-production handoff assets

Canonical Input Bundle

All validation in this execution must consume:

• examples/scene_skill_102_runtime_semantics_rematerialization_2026-04-21

Old validation assets from the pre-hardening bundle may be read for comparison only, but may not be reused as proof.

Required Outputs

1. refreshed deterministic invocation readiness asset
2. refreshed natural-language parameter readiness asset
3. refreshed static validation asset
4. refreshed direct mock execution asset
5. refreshed pseudo-production handoff assets
6. one aggregated validation refresh report

Boundary

This execution may:

1. read the refreshed runtime-semantics bundle
2. regenerate validation JSON / markdown assets under tests/fixtures/generated_scene/ and docs/superpowers/reports/
3. regenerate validation helper directories under examples/ when the existing validation flow requires route-local outputs

This execution may not:

1. modify src/
2. modify the refreshed generated skills
3. rerun rematerialization
4. update the official board
5. start real browser / pseudo-production execution

Success Criteria

1. validation refresh assets are published for every required layer
2. all refreshed assets explicitly reference the 2026-04-21 rematerialized bundle
3. residual validation blockers are recorded instead of silently reusing stale evidence