Add model: inherit to all agents

All 26 agents now use `model: inherit` so they match whatever model
the user has configured in their main conversation.

Only `lint` keeps `model: haiku` since it's a simple task.

Fixes #69

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

plugins/compound-engineering/agents/research/best-practices-researcher.md

@@ -1,6 +1,7 @@
 ---
 name: best-practices-researcher
 description: Use this agent when you need to research and gather external best practices, documentation, and examples for any technology, framework, or development practice. This includes finding official documentation, community standards, well-regarded examples from open source projects, and domain-specific conventions. The agent excels at synthesizing information from multiple sources to provide comprehensive guidance on how to implement features or solve problems according to industry standards. <example>Context: User wants to know the best way to structure GitHub issues for their Rails project. user: "I need to create some GitHub issues for our project. Can you research best practices for writing good issues?" assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions." <commentary>Since the user is asking for research on best practices, use the best-practices-researcher agent to gather external documentation and examples.</commentary></example> <example>Context: User is implementing a new authentication system and wants to follow security best practices. user: "We're adding JWT authentication to our Rails API. What are the current best practices?" assistant: "Let me use the best-practices-researcher agent to research current JWT authentication best practices, security considerations, and Rails-specific implementation patterns." <commentary>The user needs research on best practices for a specific technology implementation, so the best-practices-researcher agent is appropriate.</commentary></example>
+model: inherit
 ---
 
 **Note: The current year is 2025.** Use this when searching for recent documentation and best practices.

plugins/compound-engineering/agents/research/framework-docs-researcher.md

@@ -1,6 +1,7 @@
 ---
 name: framework-docs-researcher
 description: Use this agent when you need to gather comprehensive documentation and best practices for frameworks, libraries, or dependencies in your project. This includes fetching official documentation, exploring source code, identifying version-specific constraints, and understanding implementation patterns. <example>Context: The user needs to understand how to properly implement a new feature using a specific library. user: "I need to implement file uploads using Active Storage" assistant: "I'll use the framework-docs-researcher agent to gather comprehensive documentation about Active Storage" <commentary>Since the user needs to understand a framework/library feature, use the framework-docs-researcher agent to collect all relevant documentation and best practices.</commentary></example> <example>Context: The user is troubleshooting an issue with a gem. user: "Why is the turbo-rails gem not working as expected?" assistant: "Let me use the framework-docs-researcher agent to investigate the turbo-rails documentation and source code" <commentary>The user needs to understand library behavior, so the framework-docs-researcher agent should be used to gather documentation and explore the gem's source.</commentary></example>
+model: inherit
 ---
 
 **Note: The current year is 2025.** Use this when searching for recent documentation and version information.

plugins/compound-engineering/agents/research/git-history-analyzer.md

@@ -1,6 +1,7 @@
 ---
 name: git-history-analyzer
 description: Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\nuser: "I've just refactored the authentication module. Can you analyze the historical context?"\nassistant: "I'll use the git-history-analyzer agent to examine the evolution of the authentication module files."\n<commentary>Since the user wants historical context about code changes, use the git-history-analyzer agent to trace file evolution, identify contributors, and extract patterns from the git history.</commentary></example> <example>Context: The user needs to understand why certain code patterns exist.\nuser: "Why does this payment processing code have so many try-catch blocks?"\nassistant: "Let me use the git-history-analyzer agent to investigate the historical context of these error handling patterns."\n<commentary>The user is asking about the reasoning behind code patterns, which requires historical analysis to understand past issues and fixes.</commentary></example>
+model: inherit
 ---
 
 **Note: The current year is 2025.** Use this when interpreting commit dates and recent changes.

plugins/compound-engineering/agents/research/repo-research-analyst.md

@@ -1,6 +1,7 @@
 ---
 name: repo-research-analyst
 description: Use this agent when you need to conduct thorough research on a repository's structure, documentation, and patterns. This includes analyzing architecture files, examining GitHub issues for patterns, reviewing contribution guidelines, checking for templates, and searching codebases for implementation patterns. The agent excels at gathering comprehensive information about a project's conventions and best practices.\n\nExamples:\n- <example>\n  Context: User wants to understand a new repository's structure and conventions before contributing.\n  user: "I need to understand how this project is organized and what patterns they use"\n  assistant: "I'll use the repo-research-analyst agent to conduct a thorough analysis of the repository structure and patterns."\n  <commentary>\n  Since the user needs comprehensive repository research, use the repo-research-analyst agent to examine all aspects of the project.\n  </commentary>\n</example>\n- <example>\n  Context: User is preparing to create a GitHub issue and wants to follow project conventions.\n  user: "Before I create this issue, can you check what format and labels this project uses?"\n  assistant: "Let me use the repo-research-analyst agent to examine the repository's issue patterns and guidelines."\n  <commentary>\n  The user needs to understand issue formatting conventions, so use the repo-research-analyst agent to analyze existing issues and templates.\n  </commentary>\n</example>\n- <example>\n  Context: User is implementing a new feature and wants to follow existing patterns.\n  user: "I want to add a new service object - what patterns does this codebase use?"\n  assistant: "I'll use the repo-research-analyst agent to search for existing implementation patterns in the codebase."\n  <commentary>\n  Since the user needs to understand implementation patterns, use the repo-research-analyst agent to search and analyze the codebase.\n  </commentary>\n</example>
+model: inherit
 ---
 
 **Note: The current year is 2025.** Use this when searching for recent documentation and patterns.