fix: complete spawn chain — market_research→design, design→reviews+roundtable

Closes the two broken links in the incubation pipeline:
- market_research now spawns company_design (Phase 1→2)
- company_design now spawns 4 design_reviews + design_roundtable (Phase 2→3/4)

Also: cleaned up design_review to use identity-driven review instead of IF/ELSE blocks

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

templates/design_review.yml

@@ -21,36 +21,22 @@ steps:
       You are reviewing a COMPANY DESIGN SPECIFICATION produced by the Crimson Leaf boardroom.
       The full design document is in the deliverables above.
 
-      Review the design from YOUR domain expertise:
+      Your review focus area: {review_focus}
 
-      IF YOU ARE SARAH (Market Intelligence):
-        - Does the design actually address the market opportunity you identified?
-        - Is the revenue model realistic given the competitive landscape?
-        - Are there market risks the board overlooked?
-        - Does the target customer profile match what the data supports?
+      Examine every section of the design through the lens of YOUR expertise.
+      Be specific — reference exact sections, agent names, template names, or
+      pipeline steps where you see issues. Generic praise or vague concerns are useless.
 
-      IF YOU ARE DAVID (CTO):
-        - Can every step in the pipeline SOP be executed with the proposed template stack?
-        - Are there missing templates or tools that need to be procured?
-        - Is the template stack minimal (no unnecessary procurement)?
-        - Are there technical dependencies or failure modes the pipeline doesn't handle?
+      The design has 10 sections: Executive Summary, Market Justification, Agent Roster,
+      Chain of Command, Template Stack, Pipeline SOP, Revenue Model, Success Metrics,
+      Risks & Mitigations, and Go/No-Go Decision.
 
-      IF YOU ARE ELENA (Operations Architect):
-        - Is the agent roster right-sized (4–8 agents, no overlapping roles)?
-        - Is the pipeline SOP complete with clear dependencies?
-        - Are there workflow gaps (steps that produce no output, or outputs no step consumes)?
-        - Is the chain of command clean (one CEO, clear management hierarchy)?
-
-      IF YOU ARE PETER (CEO):
-        - Is this company profitable? What's the path to revenue?
-        - Is the cost structure lean (agent count, template count, pipeline length)?
-        - What's the single biggest risk, and is the mitigation adequate?
-        - Would you fund this company with real capital?
+      Review ALL of them, but weight your critique toward your domain.
 
       Structure your review as:
-        1. STRENGTHS — What is solid and well-designed
+        1. STRENGTHS — What is solid and well-designed (cite specifics)
         2. CONCERNS — Issues ranked by severity (critical → minor)
-        3. SPECIFIC CHANGES — Exact modifications you'd make
+        3. SPECIFIC CHANGES — Exact modifications you would make, with reasoning
         4. VERDICT — approve / revise / redesign — and why
 
   - type: reply