feat: add generated scene skill platform hardening
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
# Sweep 012 Materialization Recovery Design
|
||||
|
||||
> Date: 2026-04-20
|
||||
> Parent Plan: `2026-04-19-scene-skill-102-final-materialization-plan.md`
|
||||
|
||||
## Intent
|
||||
|
||||
Recover the single failed final materialization package:
|
||||
|
||||
`sweep-012-scene / 业扩报装管理制度`
|
||||
|
||||
The official framework board expects this scene to be `paginated_enrichment / A`, but final materialization fell into `host_bridge_workflow / C` and failed before writing required skill files.
|
||||
|
||||
## Scope
|
||||
|
||||
Allowed:
|
||||
|
||||
1. Diagnose why this one scene materializes as `host_bridge_workflow`.
|
||||
2. Apply the smallest bounded correction needed for this scene to materialize.
|
||||
3. Re-run only `sweep-012-scene` into the existing final materialization root.
|
||||
4. Refresh final materialization manifest, failures asset, human-readable index, and deterministic readiness for this scene.
|
||||
5. Publish a recovery report.
|
||||
|
||||
Forbidden:
|
||||
|
||||
1. Do not rerun all 102 scenes.
|
||||
2. Do not change other scene packages unless shared metadata refresh requires aggregate indexes.
|
||||
3. Do not start static, mock, or production validation.
|
||||
4. Do not update the official execution board.
|
||||
5. Do not create a new family.
|
||||
|
||||
## Completion Criteria
|
||||
|
||||
1. `sweep-012-scene` has `SKILL.toml`, `SKILL.md`, `scene.toml`, and at least one script.
|
||||
2. `sweep-012-scene` deterministic suffix is `。。。`.
|
||||
3. Full-name deterministic dispatch selects `sweep-012-scene`.
|
||||
4. Final materialization failure count becomes `0`.
|
||||
Reference in New Issue
Block a user