97 lines
3.1 KiB
Markdown
97 lines
3.1 KiB
Markdown
# Sweep 012 Materialization Recovery Plan
|
|
|
|
> Date: 2026-04-20
|
|
> Design: `2026-04-20-sweep-012-materialization-recovery-design.md`
|
|
|
|
## Plan Intent
|
|
|
|
Recover the only failed final materialization scene package and refresh final materialization/readiness assets to reach `102 / 102` materialized packages.
|
|
|
|
## Fixed Input
|
|
|
|
`sweep-012-scene / 业扩报装管理制度`
|
|
|
|
Source directory:
|
|
|
|
`D:/desk/智能体资料/全量业务场景/一平台场景/业扩报装管理制度`
|
|
|
|
Final output root:
|
|
|
|
`examples/scene_skill_102_final_materialization_2026-04-19`
|
|
|
|
## Allowed Files
|
|
|
|
1. `src/generated_scene/analyzer.rs`
|
|
2. `src/generated_scene/generator.rs`
|
|
3. `tests/scene_generator_test.rs`
|
|
4. `examples/scene_skill_102_final_materialization_2026-04-19/skills/sweep-012-scene/**`
|
|
5. `examples/scene_skill_102_final_materialization_2026-04-19/SCENE_INDEX.md`
|
|
6. `examples/scene_skill_102_final_materialization_2026-04-19/scene_skill_102_index.json`
|
|
7. `tests/fixtures/generated_scene/scene_skill_102_final_materialization_manifest_2026-04-19.json`
|
|
8. `tests/fixtures/generated_scene/scene_skill_102_final_materialization_failures_2026-04-19.json`
|
|
9. `tests/fixtures/generated_scene/scene_skill_102_deterministic_invocation_readiness_after_keyword_refinement_2026-04-20.json`
|
|
10. `docs/superpowers/reports/2026-04-20-sweep-012-materialization-recovery-report.md`
|
|
|
|
## Forbidden Files
|
|
|
|
1. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
2. other final skill package scripts outside `sweep-012-scene`
|
|
3. production/static/mock validation assets
|
|
|
|
## Phase 0: Diagnose Single-Scene Failure
|
|
|
|
### Tasks
|
|
|
|
1. Reproduce current failure for `sweep-012-scene`.
|
|
2. Compare analyzer output with official framework expectation.
|
|
3. Identify whether the failure is route selection, missing bootstrap, or workflow contract recovery.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Root cause is stated before implementation.
|
|
|
|
## Phase 1: Apply Minimal Recovery
|
|
|
|
### Tasks
|
|
|
|
1. Make the smallest code or fixture correction needed for `sweep-012-scene`.
|
|
2. Add or update a focused regression test.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Existing G3/G6 route behavior remains protected.
|
|
2. The correction is not generalized beyond evidence-supported behavior.
|
|
|
|
## Phase 2: Re-materialize Sweep 012 Only
|
|
|
|
### Tasks
|
|
|
|
1. Run `sg_scene_generate` only for `sweep-012-scene`.
|
|
2. Verify required files exist.
|
|
3. Normalize human-readable metadata and deterministic invocation metadata for this package.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. `sweep-012-scene` package is complete.
|
|
2. Its `scene.toml` uses suffix `。。。`.
|
|
|
|
## Phase 3: Refresh Assets
|
|
|
|
### Tasks
|
|
|
|
1. Patch final materialization manifest for `sweep-012-scene`.
|
|
2. Clear final materialization failures.
|
|
3. Refresh `SCENE_INDEX.md` and `scene_skill_102_index.json`.
|
|
4. Refresh deterministic readiness after keyword refinement.
|
|
5. Publish recovery report.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Materialized count is `102`.
|
|
2. Failure count is `0`.
|
|
3. Deterministic dispatch ready count is `102`.
|
|
|
|
## Stop Statement
|
|
|
|
Stop after `sweep-012-scene` recovery assets and report are published. Do not start static/mock/production validation under this plan.
|