fix: correct invalid Gemini CLI tool names in agents and docs

Replace `search_files` with `search_file_content` and `replace_in_file`
with `replace` across all agent frontmatter and documentation.
These were not valid Gemini CLI built-in tool names and caused agent
loading failures at startup (validation error: `tools.N: Invalid tool name`).

The terminology tables in docs/ that mapped Claude Code tools to
Gemini CLI equivalents were the source of the incorrect names, which
had propagated into 18 agent files.

Fixes #34

Author: Jamkris

agents/architect.md

@@ -1,7 +1,7 @@
 ---
 name: architect
 description: Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.
-tools: ["read_file", "search_files", "list_directory"]
+tools: ["read_file", "search_file_content", "list_directory"]
 ---
 
 You are a senior software architect specializing in scalable, maintainable system design.

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_files", "list_directory", "run_shell_command", "replace_in_file", "write_file"]
+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/code-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: code-reviewer
 description: Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
-tools: ["read_file", "search_files", "list_directory", "run_shell_command"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command"]
 ---
 
 You are a senior code reviewer ensuring high standards of code quality and security.

agents/cpp-build-resolver.md

@@ -1,7 +1,7 @@
 ---
 name: cpp-build-resolver
 description: C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
-tools: ["read_file", "write_file", "replace_in_file", "run_shell_command", "search_files", "list_directory"]
+tools: ["read_file", "write_file", "replace", "run_shell_command", "search_file_content", "list_directory"]
 ---
 
 # C++ Build Error Resolver

agents/cpp-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: cpp-reviewer
 description: Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
-tools: ["read_file", "search_files", "list_directory", "run_shell_command"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command"]
 ---
 
 You are a senior C++ code reviewer ensuring high standards of modern C++ and best practices.

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_files", "mcp__context7__resolve-library-id", "mcp__context7__query-docs"]
+tools: ["read_file", "search_file_content", "mcp__context7__resolve-library-id", "mcp__context7__query-docs"]
 ---
 
 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/flutter-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: flutter-reviewer
 description: Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
-tools: ["read_file", "search_files", "list_directory", "run_shell_command"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command"]
 ---
 
 You are a senior Flutter and Dart code reviewer ensuring idiomatic, performant, and maintainable code.

agents/harness-optimizer.md

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

agents/java-build-resolver.md

@@ -1,7 +1,7 @@
 ---
 name: java-build-resolver
 description: Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.
-tools: ["read_file", "write_file", "replace_in_file", "run_shell_command", "search_files", "list_directory"]
+tools: ["read_file", "write_file", "replace", "run_shell_command", "search_file_content", "list_directory"]
 ---
 
 # Java Build Error Resolver

agents/java-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: java-reviewer
 description: Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.
-tools: ["read_file", "search_files", "list_directory", "run_shell_command"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command"]
 ---
 You are a senior Java engineer ensuring high standards of idiomatic Java and Spring Boot best practices.
 When invoked: