2.5 KiB
2.5 KiB
Generated Scene Source Evidence Cross-Scan Plan
Date: 2026-04-20 Status: Draft Parent roadmap:
docs/superpowers/plans/2026-04-20-generated-scene-source-first-runtime-semantics-hardening-plan.mdParent design:docs/superpowers/specs/2026-04-20-generated-scene-source-evidence-cross-scan-design.md
Goal
Perform a bounded source-first cross-scan over the original 102 scene directories so the project can identify which scenes share the same runtime-semantics risk family as sweep-030-scene.
This plan is analysis-only.
Fixed Inputs
tests/fixtures/generated_scene/scene_skill_102_final_materialization_manifest_2026-04-19.jsontests/fixtures/generated_scene/scene_execution_board_2026-04-18.json- source root:
D:/desk/智能体资料/全量业务场景/一平台场景
Boundaries
Allowed:
- map the current 102 scenes to original source directories
- scan bounded source evidence
- publish JSON inventory and report
Forbidden:
- no edits in
src/ - no edits to generated skills
- no rematerialization
- no validation reruns
- no execution board updates
Phase 0: Freeze Scene Mapping
Tasks:
- derive the exact 102-scene source directory mapping
- validate that each scene maps to one source directory or an explicit missing record
Acceptance:
- all 102 scenes have a source mapping status
Phase 1: Run Bounded Source Evidence Scan
Tasks:
- scan for alias evidence
- scan for dictionary evidence
- scan for default parameter evidence
- scan for request mapping evidence
- scan for runtime URL evidence
Acceptance:
- each scene has evidence flags
- representative evidence files are recorded where found
Phase 2: Build Cross-Scan Ledger
Tasks:
- write one record per scene
- tag scenes with source-side risk hints
- explicitly identify scenes that look similar to
sweep-030-scene
Acceptance:
- all 102 scenes appear in the ledger
- the anchor case is clearly represented
Phase 3: Publish Assets
Deliverables:
tests/fixtures/generated_scene/generated_scene_source_evidence_cross_scan_2026-04-20.jsondocs/superpowers/reports/2026-04-20-generated-scene-source-evidence-cross-scan-report.md
Acceptance:
- the JSON can be used as the next input to the runtime-semantics ledger stage
- the report summarizes the five evidence families across the 102-scene set
Stop Statement
Stop after publishing the JSON inventory and report.
Do not start rule-hardening or rematerialization in this plan.