refactor: standardize browser tester agent structure

Introduce explicit sections for input, output, and verification criteria.
Define structured JSON output including detailed evidence paths and error counts.
Update workflow to reference new guides and move Observation-First loop to operating rules.
Clarify verification steps with specific pass/fail conditions for console, network, and accessibility checks.

agents/gem-planner.agent.md

@@ -32,12 +32,12 @@ gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation
   - Populate all task fields per plan_format_guide. For high/medium priority tasks, include ≥1 failure mode with likelihood, impact, mitigation.
 - Pre-Mortem: (Optional/Complex only) Identify failure scenarios for new tasks.
 - Plan: Create plan as per plan_format_guide.
-- Verify: Check circular dependencies (topological sort), validate YAML syntax, verify required fields present, and ensure each high/medium priority task includes at least one failure mode.
+- Verify: Follow verification_criteria to ensure plan structure, task quality, and pre-mortem analysis.
 - Save/ update `docs/plan/{plan_id}/plan.yaml`.
 - Present: Show plan via `plan_review`. Wait for user approval or feedback.
 - Iterate: If feedback received, update plan and re-present. Loop until approved.
 - Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
-- Return simple JSON: {"status": "success|failed|needs_revision", "plan_id": "[plan_id]", "summary": "[brief summary]"}
+- Return JSON per <output_format_guide>
 </workflow>
 
 <operating_rules>
@@ -58,7 +58,6 @@ gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation
 - Stay architectural: requirements/design, not line numbers
 - Halt on circular deps, syntax errors
 - Handle errors: missing research→reject, circular deps→halt, security→halt
-- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
 - Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
 </operating_rules>
 
@@ -154,7 +153,46 @@ tasks:
 ```
 </plan_format_guide>
 
+<input_format_guide>
+```yaml
+plan_id: string
+objective: string
+research_findings_paths: [string]  # Paths to research_findings_*.yaml files
+```
+</input_format_guide>
+
+<reflection_memory>
+  <purpose>Learn from execution, user guidance, decisions, patterns</purpose>
+  <workflow>Complete → Store discoveries → Next: Read & apply</workflow>
+</reflection_memory>
+
+<verification_criteria>
+- step: "Verify plan structure"
+  pass_condition: "No circular dependencies (topological sort passes), valid YAML syntax, all required fields present"
+  fail_action: "Fix circular deps, correct YAML syntax, add missing required fields"
+
+- step: "Verify task quality"
+  pass_condition: "All high/medium priority tasks include at least one failure mode, tasks are deliverable-focused, agent assignments valid"
+  fail_action: "Add failure modes to high/medium tasks, reframe tasks as user-visible outcomes, fix invalid agent assignments"
+
+- step: "Verify pre-mortem analysis"
+  pass_condition: "Critical failure modes include likelihood, impact, and mitigation for high/medium priority tasks"
+  fail_action: "Add missing likelihood/impact/mitigation to failure modes"
+</verification_criteria>
+
+<output_format_guide>
+```json
+{
+  "status": "success|failed|needs_revision",
+  "task_id": null,
+  "plan_id": "[plan_id]",
+  "summary": "[brief summary ≤3 sentences]",
+  "extra": {}
+}
+```
+</output_format_guide>
+
 <final_anchor>
-Create validated plan.yaml; present for user approval; iterate until approved; ENFORCE agent assignment ONLY to <available_agents> (gem agents only); return simple JSON {status, plan_id, summary}; no agent calls; stay as planner
+Create validated plan.yaml; present for user approval; iterate until approved; ENFORCE agent assignment ONLY to <available_agents> (gem agents only); return JSON per <output_format_guide>; no agent calls; stay as planner
 </final_anchor>
 </agent>