fix(agents): address code review feedback on MCP tool assignments

- Fix checklist phrasing in logic-reviewer to match boolean assertion style
- Make quick-scout workflow more prescriptive for haiku model
- Bump security-reviewer dev_refs to high-impact (taint tracking)
- Drop unused dev_health and dev_status columns from matrix
- Add footnote explaining code-reviewer is an orchestrator

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: prosdev

.claude/agents/logic-reviewer.md

@@ -70,7 +70,7 @@ Use `dev_refs` to trace caller/callee chains across package boundaries. Use `dev
 - [ ] Core exports consumed correctly by CLI, MCP server, and subagents — verify with `dev_refs`
 - [ ] Type boundaries between packages match (no `any` casting to bridge mismatches)
 - [ ] Logger (@prosdevlab/kero) configuration consistent across consumers
-- [ ] Use `dev_patterns` to check if error handling patterns are consistent with existing code
+- [ ] Error handling patterns are consistent with existing code (verify with `dev_patterns`)
 
 ## Design Echo Pass (Deep+ Effort)
 

.claude/agents/pr-composer.md

@@ -1,7 +1,7 @@
 ---
 name: pr-composer
 description: "Prepares code for pull request. Runs validation, reviews diff, and composes PR description. Use after completing a feature or fix."
-tools: Read, Glob, Grep, Bash, mcp__dev-agent__dev_map, mcp__dev-agent__dev_status
+tools: Read, Glob, Grep, Bash, mcp__dev-agent__dev_map
 model: sonnet
 ---
 
@@ -31,7 +31,7 @@ git diff main...HEAD
 git log main..HEAD --oneline
 ```
 
-Use `dev_map` to understand the structural impact of changes and identify which areas of the codebase were modified. Use `dev_status` to verify the index is healthy before PR.
+Use `dev_map` to understand the structural impact of changes and identify which areas of the codebase were modified.
 
 Review all changes for:
 

.claude/agents/quick-scout.md

@@ -25,9 +25,9 @@ Do NOT guess at architectural reasoning or make recommendations.
 
 ## Workflow
 
-1. **Search** — Start with `dev_search` for conceptual queries ("authentication flow", "error handling"). Fall back to Grep for exact string matches and Glob for file patterns.
-2. **Trace** — Use `dev_refs` to find callers/callees when tracing usage across packages. Faster and more complete than grepping for function names.
-3. **Map** — Use `dev_map` when asked about codebase structure or to identify high-churn areas.
+1. **Search** — Always start with `dev_search`. It finds code by meaning, not just keywords. Only fall back to Grep for exact string matches or Glob for file patterns.
+2. **Trace** — For "who calls X?" or "what does X call?", use `dev_refs`. Do not grep for function names when `dev_refs` can trace the graph directly.
+3. **Map** — For "what's the structure?" or "what changed recently?", use `dev_map`.
 4. **Verify** — Read the file to confirm the match
 5. **Report** — Concise, factual answer with file paths and line numbers
 

CLAUDE.md

@@ -107,19 +107,21 @@ research-planner  — investigation planning before implementation
 Agents dogfood the dev-agent MCP tools. ★ = high impact, ● = useful.
 
 ```
-┌───────────────────┬────────────┬──────────┬─────────┬──────────────┬────────────┬────────────┐
-│       Agent       │ dev_search │ dev_refs │ dev_map │ dev_patterns │ dev_status │ dev_health │
-├───────────────────┼────────────┼──────────┼─────────┼──────────────┼────────────┼────────────┤
-│ bug-investigator  │     ★      │    ★     │    ●    │              │            │            │
-│ quick-scout       │     ★      │    ★     │    ●    │              │            │            │
-│ research-planner  │     ★      │    ●     │    ★    │      ★       │            │            │
-│ logic-reviewer    │     ●      │    ★     │         │      ●       │            │            │
-│ security-reviewer │     ★      │    ●     │         │      ★       │            │            │
-│ quality-reviewer  │     ●      │          │         │      ★       │            │            │
-│ plan-reviewer     │            │    ★     │    ★    │      ●       │            │            │
-│ pr-composer       │            │          │    ●    │              │     ●      │            │
-│ code-reviewer     │            │          │         │              │            │            │
-└───────────────────┴────────────┴──────────┴─────────┴──────────────┴────────────┴────────────┘
+┌───────────────────┬────────────┬──────────┬─────────┬──────────────┐
+│       Agent       │ dev_search │ dev_refs │ dev_map │ dev_patterns │
+├───────────────────┼────────────┼──────────┼─────────┼──────────────┤
+│ bug-investigator  │     ★      │    ★     │    ●    │              │
+│ quick-scout       │     ★      │    ★     │    ●    │              │
+│ research-planner  │     ★      │    ●     │    ★    │      ★       │
+│ logic-reviewer    │     ●      │    ★     │         │      ●       │
+│ security-reviewer │     ★      │    ★     │         │      ★       │
+│ quality-reviewer  │     ●      │          │         │      ★       │
+│ plan-reviewer     │            │    ★     │    ★    │      ●       │
+│ pr-composer       │            │          │    ●    │              │
+│ code-reviewer*    │            │          │         │              │
+└───────────────────┴────────────┴──────────┴─────────┴──────────────┘
+
+* code-reviewer is an orchestrator — it delegates to security/logic/quality reviewers.
 ```
 
 ---