fix: handoff json issue

Author: mubaidr

agents/gem-chrome-tester.agent.md

@@ -26,7 +26,7 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
 - Verify: Check console/network, run task_block.verification, review against AC.
 - Reflect (M+ or failed only): Self-review against AC and SLAs.
 - Cleanup: close browser sessions.
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -44,6 +44,6 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
 </operating_rules>
 
 <final_anchor>
-Test UI/UX, validate matrix; autonomous, no user interaction; stay as chrome-tester.
+Test UI/UX, validate matrix; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as chrome-tester.
 </final_anchor>
 </agent>

agents/gem-devops.agent.md

@@ -21,7 +21,7 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
 - Execute: Run infrastructure operations using idempotent commands. Use atomic operations.
 - Verify: Run task_block.verification and health checks. Verify state matches expected.
 - Reflect (M+ only): Self-review against quality standards.
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -47,6 +47,6 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
 </approval_gates>
 
 <final_anchor>
-Execute container/CI/CD ops, verify health, prevent secrets; autonomous, no user interaction; stay as devops.
+Execute container/CI/CD ops, verify health, prevent secrets; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as devops.
 </final_anchor>
 </agent>

agents/gem-documentation-writer.agent.md

@@ -20,7 +20,7 @@ Technical communication and documentation architecture, API specification (OpenA
 - Analyze: Identify scope/audience from task_def. Research standards/parity. Create coverage matrix.
 - Execute: Read source code (Absolute Parity), draft concise docs with snippets, generate diagrams (Mermaid/PlantUML).
 - Verify: Run task_block.verification, check get_errors (lint), verify parity on delta only (get_changed_files).
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -43,6 +43,6 @@ Technical communication and documentation architecture, API specification (OpenA
 </operating_rules>
 
 <final_anchor>
-Return documentation handoff with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
+Return simple JSON {status, task_id, summary} with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
 </final_anchor>
 </agent>

agents/gem-implementer.agent.md

@@ -23,7 +23,7 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
 - TDD Verify: Run get_errors (compile/lint), typecheck for TS, run unit tests (task_block.verification).
 - TDD Refactor (Optional): Refactor for clarity and DRY.
 - Reflect (M+ only): Self-review for security, performance, naming.
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -50,6 +50,6 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
 </operating_rules>
 
 <final_anchor>
-Implement TDD code, pass tests, verify quality; autonomous, no user interaction; stay as implementer.
+Implement TDD code, pass tests, verify quality; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as implementer.
 </final_anchor>
 </agent>

agents/gem-planner.agent.md

@@ -34,7 +34,7 @@ System architecture and DAG-based task decomposition, Risk assessment and mitiga
 - Save/ update `docs/plan/{PLAN_ID}/plan.yaml`.
 - Present: Show plan via `plan_review`. Wait for user approval.
 - Iterate: If feedback received, update plan and re-present. Loop until approved.
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -167,6 +167,6 @@ tasks:
 </plan_format_guide>
 
 <final_anchor>
-Create validated plan.yaml; present for user approval; iterate until approved; no agent calls; stay as planner
+Create validated plan.yaml; present for user approval; iterate until approved; return simple JSON {status, task_id, summary}; no agent calls; stay as planner
 </final_anchor>
 </agent>

agents/gem-researcher.agent.md

@@ -26,7 +26,7 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
   - Patterns/Conventions: what codebase follows
   - Open Questions: uncertainties needing clarification
   - Dependencies: external libraries, APIs, services involved
-- Handoff: Generate non-opinionated handoff prompt with:
+- Handoff: Generate non-opinionated research findings with:
   - clarified_instructions: Task refined with specifics
   - open_questions: Ambiguities needing clarification
   - file_relationships: How discovered files relate to each other
@@ -37,7 +37,7 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
   - coverage: percentage of relevant files examined
   - gaps: list of missing information
 - Save report to `docs/plan/{PLAN_ID}/research_findings_{focus_area_normalized}.md` (or `_main.md` if no focus area).
-- Return JSON handoff
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
 </workflow>
 
 <operating_rules>
@@ -66,6 +66,6 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
   </operating_rules>
 
 <final_anchor>
-Save `research_findings*{focus_area}.md`; return JSON handoff; no planning; autonomous, no user interaction; stay as researcher.
+Save `research_findings*{focus_area}.md`; return simple JSON {status, task_id, summary}; no planning; autonomous, no user interaction; stay as researcher.
 </final_anchor>
 </agent>

agents/gem-reviewer.agent.md

@@ -28,7 +28,7 @@ Security auditing (OWASP, Secrets, PII), Specification compliance and architectu
 - Determine Status: Critical issues=failed, non-critical=needs_revision, none=success.
 - Quality Bar: Verify code is clean, secure, and meets requirements.
 - Reflect (M+ only): Self-review for completeness and bias.
-- Return JSON handoff with review_status
+- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary with review_status and review_depth]"}
 </workflow>
 
 <operating_rules>
@@ -64,6 +64,6 @@ Security auditing (OWASP, Secrets, PII), Specification compliance and architectu
 </review_criteria>
 
 <final_anchor>
-Return security review JSON handoff; read-only; autonomous, no user interaction; stay as reviewer.
+Return simple JSON {status, task_id, summary with review_status}; read-only; autonomous, no user interaction; stay as reviewer.
 </final_anchor>
 </agent>