feat: add generated scene skill platform hardening

docs/superpowers/specs/2026-04-18-g8-local-doc-pipeline-design.md

@@ -0,0 +1,56 @@
+# G8 Local Document Pipeline Design
+
+> Date: 2026-04-18
+> Status: Initial implementation slice
+
+## Goal
+
+Define `G8 抓取落库分析出文档型` as a separate family so local storage, SQL analysis, and document-generation scenes no longer fall back into `G1`, `G1-E`, `G6`, or `G3`.
+
+The first implementation slice is classification and fail-closed safety only.
+
+## Family Definition
+
+`G8` covers scenes where page/browser data capture is only the front half of the workflow. The business result depends on a downstream local pipeline:
+
+1. local service persistence or `selectData`
+2. SQL analysis such as `definedSqlQuery`
+3. document generation such as `docExport`
+4. optional host bridge actions
+5. optional `localhost:*` dependencies
+
+## P0 Boundary Sample
+
+`95598供电服务月报`
+
+Repo-local representative:
+
+`tests/fixtures/generated_scene/g8_local_doc_pipeline`
+
+## Contract Policy
+
+The first slice intentionally blocks runnable generation until a real G8 local document pipeline contract exists.
+
+The initial system must:
+
+1. classify as `local_doc_pipeline`
+2. preserve local pipeline evidence
+3. avoid fallback to `page_state_eval`
+4. avoid fallback to `host_bridge_workflow`
+5. avoid fallback to `single_request_table`
+6. fail closed with a stable blocker
+
+## Priority Rule
+
+When both host bridge and local document pipeline signals exist, `G8` wins over `G6`.
+
+Reason: `G6` is about host-bridge-driven query progression; `G8` is about the downstream local storage, SQL, and document production chain.
+
+## Acceptance Criteria
+
+1. representative fixture classifies as `local_doc_pipeline`
+2. local pipeline actions include `definedSqlQuery`
+3. local pipeline actions include `docExport`
+4. local pipeline actions include `selectData`
+5. generation fails closed
+6. existing `G1-E`, `G3`, `G6`, `G7`, and `G2` regressions remain green