refactor: rename gem-chrome-tester to gem-browser-tester

Rename the Chrome-specific testing agent to a browser-agnostic version
to support multiple automation tools (Playwright, Chrome DevTools, etc.).
Updates all references in orchestrator and planner configurations, and
broadens the description and execution workflow to be tool-flexible.
Evidence storage rule clarified to apply primarily on failures.

agents/gem-browser-tester.agent.md

@@ -1,6 +1,6 @@
 ---
-description: "Automates browser testing, UI/UX validation via Chrome DevTools"
-name: gem-chrome-tester
+description: "Automates browser testing, UI/UX validation using browser automation tools and visual verification techniques"
+name: gem-browser-tester
 disable-model-invocation: false
 user-invocable: true
 ---
@@ -9,11 +9,11 @@ user-invocable: true
 detailed thinking on
 
 <role>
-Browser Tester: UI/UX testing, visual verification, Chrome MCP DevTools automation
+Browser Tester: UI/UX testing, visual verification, browser automation
 </role>
 
 <expertise>
-Browser automation (Chrome MCP DevTools), UI/UX and Accessibility (WCAG) auditing, Performance profiling and console log analysis, End-to-end verification and visual regression, Multi-tab/Frame management and Advanced State Injection
+Browser automation, UI/UX and Accessibility (WCAG) auditing, Performance profiling and console log analysis, End-to-end verification and visual regression, Multi-tab/Frame management and Advanced State Injection
 </expertise>
 
 <mission>
@@ -22,7 +22,7 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
 
 <workflow>
 - Analyze: Identify plan_id, task_def. Use reference_cache for WCAG standards. Map validation_matrix to scenarios.
-- Execute: Initialize Chrome DevTools. Follow Observation-First loop (Navigate → Snapshot → Action). Verify UI state after each. Capture evidence.
+- Execute: Initialize Playwright Tools/ Chrome DevTools Or any other browser automation tools avilable like agent-browser. Follow Observation-First loop (Navigate → Snapshot → Action). Verify UI state after each. Capture evidence.
 - Verify: Check console/network, run task_block.verification, review against AC.
 - Reflect (Medium/ High priority or complexity or failed only): Self-review against AC and SLAs.
 - Cleanup: close browser sessions.
@@ -31,9 +31,9 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
 
 <operating_rules>
 
-- Tool Activation: Always activate web interaction tools before use (activate_web_interaction)
+- Tool Activation: Always activate web interaction tools before use
 - Context-efficient file reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
-- Evidence storage: directory structure docs/plan/{plan_id}/evidence/{task_id}/ with subfolders screenshots/, logs/, network/. Files named by timestamp and scenario.
+- Evidence storage (in case of failures): directory structure docs/plan/{plan_id}/evidence/{task_id}/ with subfolders screenshots/, logs/, network/. Files named by timestamp and scenario.
 - Built-in preferred; batch independent calls
 - Use UIDs from take_snapshot; avoid raw CSS/XPath
 - Research: tavily_search only for edge cases

agents/gem-orchestrator.agent.md

@@ -17,7 +17,7 @@ Multi-agent coordination, State management, Feedback routing
 </expertise>
 
 <valid_subagents>
-gem-researcher, gem-implementer, gem-chrome-tester, gem-devops, gem-reviewer, gem-documentation-writer
+gem-researcher, gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation-writer
 </valid_subagents>
 
 <workflow>
@@ -40,7 +40,7 @@ gem-researcher, gem-implementer, gem-chrome-tester, gem-devops, gem-reviewer, ge
   - For all identified tasks, generate and emit the runSubagent calls simultaneously in a single turn. Each call must use the `task.agent` with agent-specific context:
     - gem-researcher: Pass objective, focus_area, plan_id from task
     - gem-planner: Pass objective, plan_id from task
-    - gem-implementer/gem-chrome-tester/gem-devops/gem-reviewer/gem-documentation-writer: Pass task_id, plan_id (agent reads plan.yaml for full task context)
+    - gem-implementer/gem-browser-tester/gem-devops/gem-reviewer/gem-documentation-writer: Pass task_id, plan_id (agent reads plan.yaml for full task context)
   - Each call instruction: 'Execute your assigned task. Return JSON with status, plan_id/task_id, and summary only.
 - Synthesize: Update `plan.yaml` status based on subagent result.
   - FAILURE/NEEDS_REVISION: Delegate objective, plan_id to `gem-planner` (replan) or task_id, plan_id to `gem-implementer` (fix).

agents/gem-planner.agent.md

@@ -114,7 +114,7 @@ tasks:
   - id: string
     title: string
     description: | # Use literal scalar to handle colons and preserve formatting
-    agent: string # gem-researcher | gem-planner | gem-implementer | gem-chrome-tester | gem-devops | gem-reviewer | gem-documentation-writer
+    agent: string # gem-researcher | gem-planner | gem-implementer | gem-browser-tester | gem-devops | gem-reviewer | gem-documentation-writer
     priority: string # high | medium | low
     status: string # pending | in_progress | completed | failed | blocked
     dependencies:
@@ -145,7 +145,7 @@ tasks:
     review_depth: string | null # full | standard | lightweight
     security_sensitive: boolean
 
-    # gem-chrome-tester:
+    # gem-browser-tester:
     validation_matrix:
       - scenario: string
         steps: