[gem-team] token, tool call and request optimziations (#1625)

* feat: move to xml top tags for ebtter llm parsing and structure

- Orchestrator is now purely an orchestrator
- Added new calrify  phase for immediate user erequest understanding and task parsing before workflow
- Enforce review/ critic to plan instea dof 3x plan generation retries for better error handling and self-correction
- Add hins to all agents
- Optimize defitons for simplicity/ conciseness while maintaining clarity

* feat(critic): add holistic review and final review enhancements

* chore: bump marketplace version to 1.10.0

- Updated `.github/plugin/marketplace.json` to version 1.10.0.
- Revised `agents/gem-browser-tester.agent.md` to improve the BROWSER TESTER role documentation with a clearer structure, explicit role header, and organized knowledge sources section.

* refactor: streamline verification and self‑critique steps across browser‑tester, code‑simplifier, critic, and debugger agents

* feat(researcher): improve mode selection workflow and research implementation details

- Refine **Clarify** mode description to emphasize minimal research for detecting ambiguities.
- Reorder steps and clarify intent detection (`continue_plan`, `modify_plan`, `new_task`).
- Add explicit sub‑steps for presenting architectural and task‑specific clarifications.
- Update **Research** mode section with clearer initialization workflow.
- Simplify and reformat the confidence calculation comments for readability.
- Minor formatting tweaks and added blank lines for visual separation.

* Update gem-orchestrator.agent.md

* docs(gem-browser-tester): enhance BROWSER TESTER role description and clarify workflow steps- Expanded the BROWSER TESTER role with explicit responsibilities and constraints
- Reformatted the Knowledge Sources list using consistent numbered items for readability- Updated the Workflow section to detail initialization, execution, and teardown steps more clearly- Refined the Output Format and Research Format Guide structures to use proper markdown syntax
- Improved overall formatting and consistency of documentation for better maintainability

* docs: fix typo in delegation description

* feat(metadata): bump marketplace version to 1.15.0 and enrich agent documentation

The marketplace plugin metadata has been updated to reflect the newer
self‑learning multi‑agent orchestration description and the version hasbeen upgraded from 1.13.0 to 1.15.0.

Documentation for the following agents has been expanded with new
sections:

- **gem-browser-tester.agent.md** – added an “Output” section outlining
  strict JSON output rules and a new “I/O Optimization” section covering
  parallel batch operations, read efficiency, and scoping techniques.

- **gem-code-simplifier.agent.md** – similarly added “Output” and
  “I/O Optimization” sections describing concisely formatted JSON,
  parallel I/O, and batch processing best practices.

- **gem-reviewer.agent.md** – updated its output format and added
  detailed guidance on review scope, anti‑patterns, and I/O strategies.

These changes provide clearer usage instructions and performance‑focused
recommendations for the agents while aligning the marketplace metadata
with the updated version.

* feat(plugin): add agents list and README for gem-team plugin

* docs: update readme

* chore: match version with gem-team

* docs: standardize execution order and output format sections in agent documentation

* docs: fix typo in agent documentation files

* refactor: replace "framework" with "harness" in gem‑team marketplace, plugin, and README descriptions

agents/gem-orchestrator.agent.md

@@ -209,12 +209,15 @@ Delegate in parallel (up to 4 concurrent):
 - IF blocked with no path forward: Escalate to user with context
 - IF needs_replan: Delegate to gem-planner with failure context
 - Log all failures to docs/plan/{plan_id}/logs/
-  </workflow>
+
+</workflow>
 
 <status_summary_format>
 
 ## Status Summary Format
 
+// Be concise: omit nulls, empty arrays, verbose fields. Prefer: numbers over strings, status words over objects.
+
 ```
 Plan: {plan_id} | {plan_objective}
 Progress: {completed}/{total} tasks ({percent}%)
@@ -238,6 +241,11 @@ Blocked tasks: task_id, why blocked, how long waiting
 - Batch independent delegations (up to 4 parallel)
 - Retry: 3x
 
+### Output
+
+- NO preamble, NO meta commentary, NO explanations unless failed
+- Output ONLY valid JSON matching Status Summary Format exactly
+
 ### Constitutional
 
 - IF subagent fails 3x: Escalate to user. Never silently skip
@@ -245,6 +253,31 @@ Blocked tasks: task_id, why blocked, how long waiting
 - IF confidence < 0.85: Max 2 self-critique loops, then proceed or escalate
 - Always use established library/framework patterns
 
+### I/O Optimization
+
+Run I/O and other operations in parallel and minimize repeated reads.
+
+#### Batch Operations
+
+- Batch and parallelize independent I/O calls: `read_file`, `file_search`, `grep_search`, `semantic_search`, `list_dir` etc. Reduce sequential dependencies.
+- Use OR regex for related patterns: `password|API_KEY|secret|token|credential` etc.
+- Use multi-pattern glob discovery: `**/*.{ts,tsx,js,jsx,md,yaml,yml}` etc.
+- For multiple files, discover first, then read in parallel.
+- For symbol/reference work, gather symbols first, then batch `vscode_listCodeUsages` before editing shared code to avoid missing dependencies.
+
+#### Read Efficiently
+
+- Read related files in batches, not one by one.
+- Discover relevant files (`semantic_search`, `grep_search` etc.) first, then read the full set upfront.
+- Avoid line-by-line reads to avoid round trips. Read whole files or relevant sections in one call.
+
+#### Scope & Filter
+
+- Narrow searches with `includePattern` and `excludePattern`.
+- Exclude build output, and `node_modules` unless needed.
+- Prefer specific paths like `src/components/**/*.tsx`.
+- Use file-type filters for grep, such as `includePattern="**/*.ts"`.
+
 ### Anti-Patterns
 
 - Executing tasks directly