Files
claw/docs/superpowers/specs/2026-04-20-scene-skill-102-full-direct-mock-execution-design.md

77 lines
2.3 KiB
Markdown

# Scene Skill 102 Full Direct Mock Execution Design
> Date: 2026-04-20
> Status: Draft
> Upstream Mock Harness: `docs/superpowers/plans/2026-04-20-scene-skill-102-mock-runtime-harness-implementation-plan.md`
> Input Harness Results: `tests/fixtures/generated_scene/scene_skill_102_mock_runtime_harness_results_2026-04-20.json`
## Intent
Extend mock runtime validation from representative execution to direct execution of all `102` materialized scene skills.
This design remains strictly local and mock-only. It does not perform real browser execution, production system access, or business-data validation.
## Current Baseline
The previous mock runtime harness run produced:
| Status | Count |
| --- | ---: |
| representative `mock-runtime-pass` | 19 |
| representative failures | 0 |
That result proves archetype-level representative viability, but it does not prove every generated script can directly execute in a mock runtime.
## Goal
Produce a direct mock runtime result for all `102` materialized skills.
Each scene must receive exactly one of:
1. `direct-mock-pass`
2. `direct-mock-partial`
3. `direct-mock-fail`
## Validation Boundary
Allowed:
1. read final generated skill packages
2. load generated scripts in Node
3. inject fake runtime dependencies
4. invoke `buildBrowserEntrypointResult`
5. write direct mock result assets and report
Forbidden:
1. do not modify generated skill packages
2. do not modify `src/generated_scene/analyzer.rs`
3. do not modify `src/generated_scene/generator.rs`
4. do not rematerialize skills
5. do not update official board
6. do not open a real browser
7. do not access real network or production systems
8. do not claim production pass
## Expected Output
1. `tests/fixtures/generated_scene/scene_skill_102_full_direct_mock_execution_2026-04-20.json`
2. `docs/superpowers/reports/2026-04-20-scene-skill-102-full-direct-mock-execution-report.md`
## Interpretation
If all `102` scenes pass direct mock execution, the project can say:
`102 / 102 generated skills can load and execute their primary entrypoint under controlled fake dependencies.`
It still cannot say:
`102 / 102 generated skills are production-ready.`
## Stop Rule
Stop after direct mock results and report are published.
Do not start pseudo-production batch selection under this design.