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.
This commit is contained in:
Muhammad Ubaid Raza
2026-02-16 13:42:29 +05:00
parent 7855e66af8
commit 448ad46e72
4 changed files with 12 additions and 12 deletions

View File

@@ -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).