feat: add generated scene skill platform hardening

docs/superpowers/reports/2026-04-19-known-family-timeout-diagnostic-report.md

@@ -0,0 +1,33 @@
+# Known-Family Timeout Diagnostic Report
+
+> Date: 2026-04-19
+> Roadmap: `docs/superpowers/plans/2026-04-19-102-full-sweep-improvement-roadmap-plan.md`
+> Result: `tests/fixtures/generated_scene/known_family_timeout_diagnostic_2026-04-19.json`
+
+## Scope
+
+This report covers only the `4` records labeled `timeout-known-family-sample` by the full-sweep triage.
+
+No scene status was promoted from this diagnostic.
+
+## Result
+
+| Scene | Group | Diagnostic result |
+| --- | --- | --- |
+| `台区线损大数据-月_周累计线损率统计分析` | `G2` | `known-family-rerun-pass` |
+| `白银线损周报` | `G2` | `known-family-rerun-pass` |
+| `线损同期差异报表` | `G2` | `known-family-rerun-pass` |
+| `线损大数据-窃电分析` | `G2` | `known-family-rerun-pass` |
+
+All four completed as `multi_mode_request` with readiness `A` after the bounded source-scan improvement.
+
+## Interpretation
+
+The known-family timeout bucket was not a family capability failure. It was dominated by source-scale scanning cost from large static/vendor files.
+
+The diagnostic removes the main ambiguity from the timeout bucket: current `G2` code-backed samples can complete when scanning is bounded.
+
+## Stop Statement
+
+This diagnostic does not promote scenes and does not update the execution board.
+