64 lines
2.2 KiB
Markdown
64 lines
2.2 KiB
Markdown
# Generated Scene Runtime Semantics Post-Refresh Residual Closure Design
|
|
|
|
Date: 2026-04-21
|
|
|
|
Parent execution:
|
|
|
|
- `docs/superpowers/plans/2026-04-21-generated-scene-runtime-semantics-validation-refresh-execution-plan.md`
|
|
|
|
## Intent
|
|
|
|
Close the post-refresh residuals exposed by the 2026-04-21 validation refresh before any pseudo-production reuse is attempted.
|
|
|
|
## Residual Scope
|
|
|
|
This residual closure is strictly limited to the two regressions exposed by validation refresh:
|
|
|
|
1. rematerialized `scene.toml` deterministic suffix regression
|
|
2. `sweep-078-scene` TOML generation corruption
|
|
|
|
## Why A Separate Residual Stage Is Required
|
|
|
|
The validation refresh proved that the hardened bundle is not yet a stable canonical bundle for downstream execution:
|
|
|
|
1. `95` rematerialized scenes regressed from `suffix = "。。。"` to scene-name suffixes
|
|
2. `sweep-078-scene` emitted invalid TOML
|
|
|
|
These are generator / serialization residuals, not pseudo-production or runtime-environment residuals.
|
|
|
|
## Fixed Inputs
|
|
|
|
1. `tests/fixtures/generated_scene/generated_scene_runtime_semantics_rematerialization_manifest_2026-04-21.json`
|
|
2. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_deterministic_invocation_readiness_2026-04-21.json`
|
|
3. `tests/fixtures/generated_scene/scene_skill_102_runtime_semantics_static_validation_2026-04-21.json`
|
|
4. `docs/superpowers/reports/2026-04-21-generated-scene-runtime-semantics-validation-refresh-execution-report.md`
|
|
|
|
## Required Closure Targets
|
|
|
|
### Target A
|
|
|
|
Restore deterministic suffix generation semantics for rematerialized `scene.toml` outputs so deterministic validation no longer collapses to `0 / 102`.
|
|
|
|
### Target B
|
|
|
|
Identify and close the serialization path that emitted invalid TOML in `sweep-078-scene`.
|
|
|
|
## Non-Goals
|
|
|
|
This residual closure does not include:
|
|
|
|
1. pseudo-production execution
|
|
2. rematerialization of `local_doc_pipeline` residual scenes
|
|
3. runtime callback-host / helper debugging
|
|
4. service-console changes
|
|
5. new hardening routes outside the two residuals above
|
|
|
|
## Expected Downstream
|
|
|
|
After this residual closure, the next step should be:
|
|
|
|
1. rerun rematerialization execution
|
|
2. rerun validation refresh
|
|
|
|
Only then should pseudo-production selection be reconsidered.
|