feat: 3 operator approval gates (WaitingForHuman) in incubation pipeline

Gate 1: After market_research — operator selects business concept
Gate 2: After company_design — operator approves design before review cycle
Gate 3: After design_polish — operator green lights bootstrap (company creation)

Each gate is a human_action task (status: WaitingForHuman) that blocks
downstream tasks via depends_on. Operator resolves naturally via Discord.
Pipeline SOP updated with gate diagram and expanded kill conditions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

templates/company_design.yml

@@ -80,14 +80,29 @@ steps:
   - type: document
     filename: "company-design-spec-{{task_name_slug}}"
 
+  - type: reply
+    target: discussion
+    style: |
+      Present the Company Design Specification to the operator. Highlight the key
+      decisions: company name, agent roster size, template stack, and revenue model.
+      End with: "Does this design align with your vision? Reply to approve or suggest changes."
+
   - type: package
     hint: |
-      The design specification is complete. Now spawn four independent reviews —
-      one from each board member — plus a roundtable that depends on all four.
-      The roundtable will reach consensus and spawn the polish step automatically.
+      The design specification is complete and presented to the operator.
+      Spawn a human approval gate — the review cycle will NOT start until
+      the operator confirms the design direction is correct.
     schema:
       design_spec: string
     spawn:
+      - task_type: human_action
+        task_name: "Operator Review: Approve Design Direction — {task.message}"
+        agent_name: Peter
+        priority: 8
+        context:
+          design_spec: "{design_spec}"
+          gate_purpose: "Review company design spec, approve before review cycle begins"
+
       - task_type: design_review
         task_name: "Design Review (Peter): {task.message}"
         agent_name: Peter
@@ -95,6 +110,8 @@ steps:
         context:
           design_spec: "{design_spec}"
           review_focus: financial_viability
+        depends_on:
+          - "Operator Review: Approve Design Direction — {task.message}"
 
       - task_type: design_review
         task_name: "Design Review (David): {task.message}"
@@ -103,6 +120,8 @@ steps:
         context:
           design_spec: "{design_spec}"
           review_focus: technical_feasibility
+        depends_on:
+          - "Operator Review: Approve Design Direction — {task.message}"
 
       - task_type: design_review
         task_name: "Design Review (Sarah): {task.message}"
@@ -111,6 +130,8 @@ steps:
         context:
           design_spec: "{design_spec}"
           review_focus: market_fit
+        depends_on:
+          - "Operator Review: Approve Design Direction — {task.message}"
 
       - task_type: design_review
         task_name: "Design Review (Elena): {task.message}"
@@ -119,6 +140,8 @@ steps:
         context:
           design_spec: "{design_spec}"
           review_focus: operational_completeness
+        depends_on:
+          - "Operator Review: Approve Design Direction — {task.message}"
 
       - task_type: design_roundtable
         task_name: "Design Roundtable: {task.message}"