* <think>The user wants me to generate a conventional format commit message based on the git diff output provided.
Let me analyze the changes:
1. **`.github/plugin/marketplace.json`**:
- Updated the "gem-team" plugin description to include "complexity-aware research, multi-plan selection for critical tasks"
- Updated version from "1.2.1" to "1.3.0"
2. **`agents/gem-browser-tester.agent.md`**:
- Added `<tools>` section with new tools: get_errors, mcp_io_github_chr_performance_start_trace, mcp_io_github_chr_performance_analyze_insight
- Modified the `<expertise>` section (moved closing tag)
- Updated `<input_format_guide>` to use proper JSON code block format
- Updated `<output_format_guide>` to add "needs_revision" status option and restructured JSON formatting
- Updated `<constraints>` section - significantly changed the guidelines
This appears to be an update to:
- Plugin marketplace version bump
- Browser tester agent improvements (new tools, updated workflow constraints, better formatting)
Let me generate a conventional commit message:
- Type: Could be "feat" for new features or "chore" for maintenance
- Scope: could be "marketplace" and "browser-tester"
- Message should describe the changes succinctly
Looking at the changes more carefully:
- Plugin version bump from 1.2.1 to 1.3.0 - this is a feature update
- New tools added to browser tester agent
- Updated constraints/workflow for browser tester
I'll create a commit message that captures the essence:
</think>
feat: update gem-team to v1.3.0 and enhance browser-tester agent
- Bump gem-team plugin version from 1.2.1 to 1.3.0 with updated description
- Add performance tracing and insight tools to browser-tester agent
- Refactor input/output format guides with proper JSON code blocks
- Update agent constraints with improved tool usage and batching guidelines
* fix: correct typo "suiteable" to "suitable" in agent documentation
- Make browser tester generic to support for chrome devotols mcp, playwright, agentic browser tools.
- Add Team lead and energetci peronsality to Orchestrator
- Add progress updates between phases/ waves
* feat: Prd/ steer support
- Add supprot for PRD
- Vscode steer/ queue support
- Consistent artifacts
- Improved parallel running; for researchers too
* chore: improve prd update support
* chore: Make reviewer use prd for compaince
* chore: imrpvoe websearch in researcher
* fix(gem-team): revert gem-team plugin version from 1.5.0 to 1.2.0
- Refined `gem-browser-tester` workflow to separate initialization from
execution and enforce an Observation-First loop.
- Added retry logic for transient failures (e.g., timeouts, network issues)
in browser automation tasks.
- Standardized artifact generation paths to `docs/plan/{plan_id}/`
across multiple agents.
- Updated failure actions to specify evidence capture locations
(logs, network) for improved debugging and traceability.
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.
- Remove redundant `<mission>` section from gem-browser-tester
- Add "Reflect" step to gem-documentation-writer for self-review on high-priority or failed tasks
- Refactor gem-orchestrator completion phase to generate a walkthrough markdown file instead of a review
- Update orchestrator rules to allow direct execution for creating walkthrough files
Remove "detailed thinking on" directive and consolidate operating_rules sections for consistency. Both gem-browser-tester.agent.md and gem-devops.agent.md now share standardized rules: unified tool activation phrasing ("Always activate tools before use"), merged context-efficient reading instructions, and removed agent-specific variations. This simplifies maintenance and ensures consistent behavior across different agent types while preserving core functionality like evidence storage, error handling, and output constraints.
- Introduced new agents: gem-chrome-tester, gem-devops, gem-documentation-writer, gem-implementer, gem-orchestrator, gem-planner, gem-researcher, and gem-reviewer.
- Updated README.collections.md to include the new Gem Team Multi-Agent Orchestration collection.
- Created gem-team.collection.yml and gem-team.md for structured documentation of the multi-agent orchestration framework.
- Each agent includes detailed descriptions, workflows, operating rules, and final anchors for clarity on their functionalities and usage.
