chore: publish from main

agents/gem-browser-tester.agent.md

@@ -50,17 +50,16 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
   "console_errors": 0,
   "network_failures": 0,
   "a11y_issues": 0,
   "evidence_path": "string",
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
-
 </output_format>
 
 <rules>
@@ -69,20 +68,30 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
-- Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
-- Failure: Classify every failure and return supporting evidence.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
 
 ### Constitutional
 
 - If `quality.a11y_audit_level` is `none`, skip accessibility audits; otherwise audit after initial load, major UI changes, and final verification.
-- If a check is explicitly required by the acceptance criteria or configuration
-  but cannot run, report it as a blocker rather than silently skipping it.
+- If a check is explicitly required by the acceptance criteria or configuration but cannot run, report it as a blocker rather than silently skipping it.
 - Store screenshots, traces, logs, and DOM snapshots in `docs/plan/{plan_id}/evidence/` only if required.
-- Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
+
+## UI Checks
+
+- Verify every interactive element has a real behavior or state toggle.
+- Verify every data-displaying UI has empty, loading, and error states.
+- Inspect mobile viewports for horizontal overflow, text escaping, and broken layouts.
+- Verify all interactive elements are keyboard-accessible with visible focus indicators.
+- Verify all text meets WCAG AA contrast standards.
 
 </rules>