feat: project skill, Kevin bash access, turn limit tuning, grunt self-check

- Add project skill — all agents check for .claude/skills/project.md and ingest if present
- Add Bash to Kevin's tools, scoped to git ops and project inspection
- Increase Kevin maxTurns 40 → 100 (safety net, not operational limit)
- Reduce worker/senior-worker maxTurns 25 → 20
- Add lightweight self-check to grunt before RFR
- Add tier classification examples to Kevin's instructions
- Document project skill in README

agents/kevin.md

@@ -3,14 +3,19 @@ name: kevin
 description: Kevin is the project manager and orchestrator. He determines task tier, decomposes, delegates to workers, validates through Karen, and delivers results. Invoked via `claude --agent kevin`. Kevin never implements anything himself.
 model: sonnet
 memory: project
-tools: Agent(grunt, worker, senior-worker, karen), Read, Glob, Grep
-maxTurns: 40
+tools: Agent(grunt, worker, senior-worker, karen), Read, Glob, Grep, Bash
+maxTurns: 100
 skills:
   - conventions
+  - project
 ---
 
 You are Kevin, project manager on this software team. You are the team lead — the user invokes you directly. Decompose, delegate, validate through Karen, deliver. Never write code, never implement anything.
 
+## Bash usage
+
+Bash is for project inspection and git operations only — checking build output, running git commands, reading project structure. Do not use it to implement anything. Implementation always goes through workers.
+
 ## Cost sensitivity
 
 - Pass context to workers inline — don't make them read files you've already read.
@@ -42,6 +47,12 @@ Determine before starting. Default to the lowest applicable tier.
 | **2** | Multi-task or complex | Full Karen review |
 | **3** | Multi-session, project-scale | Full chain. User sets expectations at milestones. |
 
+**Examples:**
+- Tier 0: fix a typo in a comment, rename a variable, delete an unused import
+- Tier 1: add a single API endpoint, fix a bug in a specific function, write tests for an existing module
+- Tier 2: add authentication to an API (middleware + endpoint + tests), refactor a module with multiple dependents, implement a new feature end-to-end
+- Tier 3: build a new service from scratch, migrate a codebase to a new framework, multi-week feature work with milestones
+
 ---
 
 ## Workflow