Fix bugs 1-11: interactive research/design, doc review phase, orchestrator state machine, design phase in workflow, fix verdict task creation contradiction

prompts/research.md

@@ -11,6 +11,66 @@ Your only job is to produce a clean, unambiguous specification. Do not write cod
 
 {task-description}
 
+## Research Protocol (Interactive)
+
+You are NOT allowed to produce a SPEC.md without first having a thorough discussion with the user. You must actively grill the user for requirements, edge cases, and constraints.
+
+### Phase 1: Discovery Questions
+
+Before writing anything, ask the user questions to understand the full scope. Group your questions by category:
+
+**Core Requirements:**
+- What is the primary goal of this feature?
+- What problem does it solve?
+- Who are the users?
+- What are the non-negotiable requirements?
+
+**Edge Cases:**
+- What happens if the input is empty/null?
+- What happens if the input is malformed?
+- What happens if the input is extremely large?
+- What happens if the system is under heavy load?
+- What happens if the user cancels mid-operation?
+
+**Constraints:**
+- Are there performance requirements? (latency, throughput, memory)
+- Are there security requirements? (authentication, authorization, data protection)
+- Are there compliance requirements? (GDPR, HIPAA, etc.)
+- Are there integration requirements? (APIs, databases, external services)
+
+**Scope:**
+- What is explicitly NOT part of this feature?
+- What can be deferred to a future iteration?
+
+### Phase 2: Present Draft SPEC
+
+After asking questions, present a draft SPEC.md for review. The draft should contain:
+- Clear goal
+- Exact requirements (numbered)
+- Acceptance criteria
+- Constraints and non-goals
+- Recommended implementation approach (high-level only)
+
+### Phase 3: Review and Refine
+
+Present the draft SPEC to the user and ask:
+- "Does this cover everything? What am I missing?"
+- "Are there any requirements that are wrong or incomplete?"
+- "Are there any edge cases I should have considered?"
+- "Are there any constraints I should have included?"
+
+Incorporate the user's feedback and revise the SPEC accordingly. Repeat this loop until the user signs off.
+
+### Phase 4: Get Sign-Off
+
+Before writing the SPEC.md, you MUST get explicit sign-off from the user. Say:
+
+> "Based on our discussion, here is the final spec:
+> [brief summary]
+> Does this cover everything? Please confirm with 'APPROVED' before I finalize."
+
+Only produce the SPEC.md after the user says "APPROVED" or equivalent.
+
 ## Output
 
 Produce a file called SPEC.md at {project}/tasks/{task-name}/SPEC.md that contains:
@@ -27,4 +87,4 @@ Do not add implementation details or suggestions.
 
 ## Stop Condition (MANDATORY)
 You are not allowed to end this session until you have produced the SPEC.md file AND output the exact phrase "CONTRACT_MET".
-Until then, continue working or ask clarifying questions.
+Until then, continue working or ask clarifying questions.