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-documentation-writer.agent.md

@@ -17,11 +17,11 @@ Technical communication and documentation architecture, API specification (OpenA
 <workflow>
 - 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 verification, check get_errors (compile/lint).
+- Verify: Follow verification_criteria (completeness, accuracy, formatting, get_errors).
   * For updates: verify parity on delta only
   * For new features: verify documentation completeness against source code and acceptance_criteria
 - Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
-- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
+- Return JSON per <output_format_guide>
 </workflow>
 
 <operating_rules>
@@ -35,11 +35,59 @@ Technical communication and documentation architecture, API specification (OpenA
 - Verify parity: on delta for updates; against source code for new features
 - Never use TBD/TODO as final documentation
 - Handle errors: transient→handle, persistent→escalate
-- 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>
 
+<input_format_guide>
+```yaml
+task_id: string
+plan_id: string
+plan_path: string  # "docs/plan/{plan_id}/plan.yaml"
+task_definition: object  # Full task from plan.yaml
+  # Includes: audience, coverage_matrix, is_update, etc.
+```
+</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 documentation completeness"
+  pass_condition: "All items in coverage_matrix documented, no TBD/TODO placeholders"
+  fail_action: "Add missing documentation, replace TBD/TODO with actual content"
+
+- step: "Verify accuracy (parity with source code)"
+  pass_condition: "Documentation matches implementation (APIs, parameters, return values)"
+  fail_action: "Update documentation to match actual source code"
+
+- step: "Verify formatting and structure"
+  pass_condition: "Proper Markdown/HTML formatting, diagrams render correctly, no broken links"
+  fail_action: "Fix formatting issues, ensure diagrams render, fix broken links"
+
+- step: "Check get_errors (compile/lint)"
+  pass_condition: "No errors or warnings in documentation files"
+  fail_action: "Fix all errors and warnings"
+</verification_criteria>
+
+<output_format_guide>
+```json
+{
+  "status": "success|failed|needs_revision",
+  "task_id": "[task_id]",
+  "plan_id": "[plan_id]",
+  "summary": "[brief summary ≤3 sentences]",
+  "extra": {
+    "docs_created": [],
+    "docs_updated": [],
+    "parity_verified": true
+  }
+}
+```
+</output_format_guide>
+
 <final_anchor>
-Return simple JSON {status, task_id, summary} with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
+Return JSON per <output_format_guide> with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
 </final_anchor>
 </agent>