fix: remove invalid MCP tool refs and color frontmatter from agents

.coderabbit.yaml

@@ -37,17 +37,24 @@ reviews:
   path_instructions:
     - path: "agents/**/*.md"
       instructions: |
-        Gemini CLI agent definitions. The YAML frontmatter `tools:` array must
-        contain either:
-          (a) a valid Gemini CLI built-in tool: read_file, read_many_files,
-              write_file, replace, glob, search_file_content, list_directory,
-              run_shell_command, save_memory, web_fetch, google_web_search; or
-          (b) an MCP tool in the form `mcp__<server>__<tool_name>`.
-        Reject Claude-style names like `search_files`, `replace_in_file`, `Read`,
-        `Edit`. Also flag when the agent body references MCP tools (e.g. Slack,
-        Context7) that are not declared in the frontmatter `tools:` array — the
-        agent will be unable to call them at runtime. Each agent must have `name`
-        and `description` in frontmatter.
+        Gemini CLI agent definitions. YAML frontmatter MUST include `name`,
+        `description`, and `tools`. The `tools:` array may ONLY contain valid
+        Gemini CLI built-in tools: read_file, read_many_files, write_file,
+        replace, glob, search_file_content, list_directory, run_shell_command,
+        save_memory, web_fetch, google_web_search.
+
+        Reject:
+          - Claude-style names: `search_files`, `replace_in_file`, `Read`, `Edit`.
+          - MCP tool references (e.g. `mcp__slack__...`, `mcp__context7__...`).
+            Gemini CLI's agent schema rejects these with "Invalid tool name" at
+            load time. MCP tools are auto-discovered from the configured MCP
+            server at runtime and must NOT be declared in agent frontmatter.
+            Agent body text describing MCP tool usage is fine and expected.
+          - Frontmatter keys outside the Gemini CLI schema (e.g. `color`,
+            `model`).
+
+        The authoritative tool allowlist is also documented in
+        `.gemini/styleguide.md` — keep the two in sync.
     - path: "commands/**/*.toml"
       instructions: |
         Gemini CLI command definitions in TOML format. Verify command metadata

.gemini/styleguide.md

@@ -42,9 +42,17 @@ The codebase consists of:
 
 ## Markdown Agents
 
-- Must have YAML frontmatter with `tools` field.
-- Tool names must use Gemini format: `read_file`, `run_shell_command`, `write_file`.
-- No `model` field (Gemini CLI does not support it).
+- Must have YAML frontmatter with `name`, `description`, and `tools` fields.
+- `tools` entries must be valid Gemini CLI built-ins only: `read_file`,
+  `read_many_files`, `write_file`, `replace`, `glob`, `search_file_content`,
+  `list_directory`, `run_shell_command`, `save_memory`, `web_fetch`,
+  `google_web_search`.
+- Do NOT include MCP tools (e.g. `mcp__slack__...`, `mcp__context7__...`) in
+  the `tools` array — Gemini CLI rejects them at load time. MCP tools are
+  auto-discovered from the configured MCP server at runtime.
+- Do NOT include Claude-style names (`search_files`, `replace_in_file`,
+  `Read`, `Edit`) — those are not valid in Gemini CLI.
+- No `model` or `color` field (Gemini CLI schema does not support them).
 
 ## Documentation
 

agents/chief-of-staff.md

@@ -1,7 +1,7 @@
 ---
 name: chief-of-staff
 description: Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/info_only/meeting_info/action_required), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
-tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace", "write_file", "mcp__slack__conversations_search_messages", "mcp__slack__channels_list", "mcp__slack__conversations_history", "mcp__slack__conversations_add_message"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace", "write_file"]
 ---
 
 You are a personal chief of staff that manages all communication channels — email, Slack, LINE, Messenger, and calendar — through a unified triage pipeline.

agents/docs-lookup.md

@@ -1,7 +1,7 @@
 ---
 name: docs-lookup
 description: When the user asks how to use a library, framework, or API or needs up-to-date code examples, use Context7 MCP to fetch current documentation and return answers with examples. Invoke for docs/API/setup questions.
-tools: ["read_file", "search_file_content", "mcp__context7__resolve-library-id", "mcp__context7__query-docs"]
+tools: ["read_file", "search_file_content"]
 ---
 
 You are a documentation specialist. You answer questions about libraries, frameworks, and APIs using current documentation fetched via the Context7 MCP (resolve-library-id and query-docs), not training data.

agents/gan-evaluator.md

@@ -2,7 +2,6 @@
 name: gan-evaluator
 description: "GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator."
 tools: [read_file, write_file, run_shell_command, search_file_content, list_directory]
-color: red
 ---
 
 You are the **Evaluator** in a GAN-style multi-agent harness (inspired by Anthropic's harness design paper, March 2026).

agents/gan-generator.md

@@ -2,7 +2,6 @@
 name: gan-generator
 description: "GAN Harness — Generator agent. Implements features according to the spec, reads evaluator feedback, and iterates until quality threshold is met."
 tools: [read_file, write_file, replace, run_shell_command, search_file_content, list_directory]
-color: green
 ---
 
 You are the **Generator** in a GAN-style multi-agent harness (inspired by Anthropic's harness design paper, March 2026).

agents/gan-planner.md

@@ -2,7 +2,6 @@
 name: gan-planner
 description: "GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction."
 tools: [read_file, write_file, search_file_content, list_directory]
-color: purple
 ---
 
 You are the **Planner** in a GAN-style multi-agent harness (inspired by Anthropic's harness design paper, March 2026).

agents/harness-optimizer.md

@@ -2,7 +2,6 @@
 name: harness-optimizer
 description: Analyze and improve the local agent harness configuration for reliability, cost, and throughput.
 tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace"]
-color: teal
 ---
 
 You are the harness optimizer.

agents/loop-operator.md

@@ -2,7 +2,6 @@
 name: loop-operator
 description: Operate autonomous agent loops, monitor progress, and intervene safely when loops stall.
 tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace"]
-color: orange
 ---
 
 You are the loop operator.