feat: add generated scene skill platform hardening

docs/superpowers/plans/2026-04-20-generated-scene-rule-hardening-route-plan.md

@@ -0,0 +1,143 @@
+# Generated Scene Rule Hardening Route Plan
+
+> Date: 2026-04-20
+> Status: Draft
+> Parent roadmap:
+> - `docs/superpowers/plans/2026-04-20-generated-scene-source-first-runtime-semantics-hardening-plan.md`
+> Parent design:
+> - `docs/superpowers/specs/2026-04-20-generated-scene-rule-hardening-route-design.md`
+> Upstream ledger:
+> - `docs/superpowers/plans/2026-04-20-generated-scene-source-first-runtime-semantics-ledger-plan.md`
+
+## Plan Intent
+
+Convert the completed runtime-semantics ledger into a bounded hardening-route sequence.
+
+This stage decides execution order and the next child implementation plans. It does not change code yet.
+
+## Fixed Inputs
+
+1. `tests/fixtures/generated_scene/generated_scene_source_first_runtime_semantics_ledger_2026-04-20.json`
+2. `docs/superpowers/reports/2026-04-20-generated-scene-source-first-runtime-semantics-ledger-report.md`
+
+## Scope Guardrails
+
+Allowed:
+
+1. cluster scenes by reusable route
+2. freeze route order
+3. define bounded child implementation plans
+4. define rematerialization dependency
+5. define validation refresh dependency
+
+Forbidden:
+
+1. no implementation changes in `src/`
+2. no skill manifest changes
+3. no rematerialization execution
+4. no validation reruns
+5. no inner-network execution
+
+## Phase 0: Freeze Route Order
+
+### Objective
+
+Turn the ledger into one fixed route order for downstream implementation.
+
+### Ordered Routes
+
+1. `resolver_request_mapping_hardening`
+2. `runtime_url_classification_hardening`
+3. `embedded_dictionary_extraction_hardening`
+4. `parameter_default_semantics_recovery_hardening`
+5. `alias_generation_hardening`
+
+### Acceptance
+
+1. the order is explicit and no longer derived ad hoc during later implementation
+
+## Phase 1: Build Route Clusters
+
+### Objective
+
+Cluster scenes from the ledger into reusable route buckets.
+
+### Tasks
+
+1. count all scenes covered by each route
+2. identify the densest scene families per route
+3. identify route-local anchor scenes
+
+### Acceptance
+
+1. each route has a stable implementation bucket definition
+
+## Phase 2: Define Bounded Child Implementation Plans
+
+### Objective
+
+Create one bounded implementation child plan for each top route.
+
+### Required child plans
+
+1. `2026-04-20-generated-scene-resolver-request-mapping-hardening-plan.md`
+2. `2026-04-20-generated-scene-runtime-url-classification-hardening-plan.md`
+3. `2026-04-20-generated-scene-embedded-dictionary-extraction-hardening-plan.md`
+4. `2026-04-20-generated-scene-parameter-default-semantics-hardening-plan.md`
+5. `2026-04-20-generated-scene-invocation-alias-generation-hardening-plan.md`
+
+### Acceptance
+
+1. each child plan has a fixed scope and stop rule
+2. no child plan is scene-name hardcoded as its whole purpose
+
+## Phase 3: Declare Rematerialization Dependency
+
+### Objective
+
+Make full 102-scene rematerialization a mandatory downstream stage after route execution.
+
+### Tasks
+
+1. define `generated-scene-runtime-semantics-rematerialization-refresh-plan`
+2. freeze it as required after implementation
+
+### Acceptance
+
+1. no route may be considered complete without rematerialization
+
+## Phase 4: Declare Validation Refresh Dependency
+
+### Objective
+
+Make validation refresh mandatory after rematerialization.
+
+### Tasks
+
+1. define `generated-scene-runtime-semantics-validation-refresh-plan`
+2. require refresh of:
+   - deterministic invocation readiness
+   - natural-language parameter readiness
+   - static validation
+   - direct mock execution
+   - pseudo-production handoff
+
+### Acceptance
+
+1. no route may be considered fully closed until validation assets are refreshed
+
+## Deliverables
+
+1. route design / sequencing report
+2. route cluster JSON
+3. bounded child-plan list for the five routes
+
+## Stop Statement
+
+Stop after:
+
+1. publishing the route design / sequencing assets
+2. publishing the five child implementation plans
+3. publishing rematerialization and validation-refresh dependency plans
+
+Do not execute route implementation inside this plan.