gem-team: Add tracing to browser-tester, and improve agent docs and constraints (#1094)

* <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

plugins/gem-team/.github/plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gem-team",
-  "description": "A modular multi-agent team for complex project execution with DAG-based planning, parallel execution, TDD verification, and automated testing with energetic team lead.",
-  "version": "1.2.1",
+  "description": "A modular multi-agent team for complex project execution with DAG-based planning, complexity-aware research, multi-plan selection for critical tasks, parallel execution, TDD verification, and automated testing.",
+  "version": "1.3.0",
   "author": {
     "name": "Awesome Copilot Community"
   },

plugins/gem-team/README.md

@@ -1,6 +1,6 @@
 # Gem Team Multi-Agent Orchestration Plugin
 
-A modular multi-agent team for complex project execution with DAG-based planning, parallel execution, TDD verification, and automated testing.
+A modular multi-agent team for complex project execution with DAG-based planning, complexity-aware research, multi-plan selection for critical tasks, parallel execution, TDD verification, and automated testing.
 
 ## Installation
 
@@ -15,14 +15,14 @@ copilot plugin install gem-team@awesome-copilot
 
 | Agent | Description |
 |-------|-------------|
-| `gem-orchestrator` | Team Lead - Coordinates multi-agent workflows with energetic announcements, delegates tasks, synthesizes results via runSubagent |
-| `gem-researcher` | Research specialist: gathers codebase context, identifies relevant files/patterns, returns structured findings |
-| `gem-planner` | Creates DAG-based plans with pre-mortem analysis and task decomposition from research findings |
-| `gem-implementer` | Executes TDD code changes, ensures verification, maintains quality |
-| `gem-browser-tester` | Automates E2E scenarios with Chrome DevTools MCP, Playwright, Agent Browser. UI/UX validation using browser automation tools and visual verification techniques |
-| `gem-devops` | Manages containers, CI/CD pipelines, and infrastructure deployment |
-| `gem-reviewer` | Security gatekeeper for critical tasks—OWASP, secrets, compliance |
-| `gem-documentation-writer` | Generates technical docs, diagrams, maintains code-documentation parity |
+| `gem-orchestrator` | Team Lead - Coordinates multi-agent workflows with energetic announcements, delegates tasks, synthesizes results via runSubagent. Supports complexity detection and multi-plan selection for critical tasks. |
+| `gem-researcher` | Research specialist - gathers codebase context, identifies relevant files/patterns, returns structured findings. Uses complexity-based proportional effort (1-3 passes). |
+| `gem-planner` | Creates DAG-based plans with pre-mortem analysis and task decomposition from research findings. Calculates plan metrics for multi-plan selection. |
+| `gem-implementer` | Executes TDD code changes, ensures verification, maintains quality. Includes online research tools (Context7, tavily_search). |
+| `gem-browser-tester` | Automates E2E scenarios with Chrome DevTools MCP, Playwright, Agent Browser. UI/UX validation using browser automation tools and visual verification techniques. |
+| `gem-devops` | Manages containers, CI/CD pipelines, and infrastructure deployment. Handles approval gates with user confirmation. |
+| `gem-reviewer` | Security gatekeeper for critical tasks—OWASP, secrets, compliance. Includes PRD compliance verification for features, decisions, state machines, and error codes. |
+| `gem-documentation-writer` | Generates technical docs, diagrams, maintains code-documentation parity. |
 
 ## Source