feat: add generated scene skill platform hardening

docs/superpowers/plans/2026-04-18-g6-host-bridge-workflow-plan.md

@@ -0,0 +1,77 @@
+# G6 Host Bridge Workflow Plan
+
+> Date: 2026-04-18
+> Status: Initial implementation slice
+
+## Plan Intent
+
+Start the `G6` line after `G1-E` second-sample reuse has been validated.
+
+This plan implements the first safe slice only: classification, evidence separation, readiness gates, and fail-closed behavior.
+
+## Phase 0: Boundary Freeze
+
+Tasks:
+
+1. keep `电能表现场检验完成率指标报表` as the P0 boundary sample
+2. define the repo-local representative fixture
+3. keep `G6` separate from `G1`, `G1-E`, `G3`, `G7`, and `G8`
+
+Deliverables:
+
+1. `G6` design doc
+2. `G6` plan doc
+3. repo-local representative fixture
+
+Acceptance criteria:
+
+1. `G6` is no longer discussed as a `G1` candidate
+2. `G6` is not treated as a generic localhost-pollution case
+
+## Phase 1: Analyzer Classification
+
+Tasks:
+
+1. add `host_bridge_workflow` as a workflow archetype
+2. detect explicit host bridge actions
+3. keep `localhost:*` as supporting host-runtime evidence
+4. ensure explicit host bridge signals outrank `G1-E`
+5. ensure ordinary localhost export noise does not become `G6`
+
+Acceptance criteria:
+
+1. `g6_host_bridge_workflow` fixture classifies as `host_bridge_workflow`
+2. `bootstrap_localhost_pollution` remains a non-G6 business scene
+
+## Phase 2: Fail-Closed Gate
+
+Tasks:
+
+1. add readiness risks for missing or unsupported G6 contract
+2. add `g6_host_bridge_detected`
+3. add `g6_fail_closed`
+4. block generation before runnable output
+
+Acceptance criteria:
+
+1. `G6` generation returns a controlled error
+2. error message includes `host_bridge_workflow`
+3. no pseudo-runnable skill is produced
+
+## Phase 3: Regression
+
+Tasks:
+
+1. run scene generator regression
+2. run family regression
+3. run family policy regression
+4. run canonical regression
+
+Acceptance criteria:
+
+1. all target regressions pass
+2. no `G1-E/G3/G2` behavior regresses
+
+## Next Step
+
+After this safe G6 slice, continue to `G7 多接口盘点汇总型` boundary assessment unless G6 runtime implementation becomes the selected priority.