feat: add generated scene skill platform hardening
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# Bootstrap Target Residual Isolation Plan
|
||||
|
||||
> Date: 2026-04-19
|
||||
> Status: Draft
|
||||
> Parent Plan: `docs/superpowers/plans/2026-04-19-structured-fail-closed-residual-13-closure-plan.md`
|
||||
> Parent Route: `Residual Route D`
|
||||
> Parent Layer: `Layer D`
|
||||
|
||||
## Plan Intent
|
||||
|
||||
Isolate the remaining page-state/bootstrap-target residual without starting login recovery or runtime navigation implementation.
|
||||
|
||||
## Fixed Input Bucket
|
||||
|
||||
1. `sweep-091-scene` / `用户停电频次分析监测`
|
||||
|
||||
## Allowed Files
|
||||
|
||||
1. isolation JSON asset
|
||||
2. isolation report
|
||||
|
||||
## Forbidden Files
|
||||
|
||||
1. `src/generated_scene/analyzer.rs`
|
||||
2. `src/generated_scene/generator.rs`
|
||||
3. login/runtime implementation files
|
||||
4. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
||||
|
||||
## Tasks
|
||||
|
||||
1. preserve the residual as bootstrap-target isolated;
|
||||
2. publish isolation report;
|
||||
3. do not implement login recovery.
|
||||
|
||||
## Stop Statement
|
||||
|
||||
Stop after isolation assets are published.
|
||||
|
||||
Reference in New Issue
Block a user