add-agent-adapter

# Add a New Agent Adapter The full, current guide is `docs/agent-adapter.md`. It is the single source of truth for this task. Read it and follow it step by step. Do not add an agent adapter from memory. The adapter pattern touches several files across `agent/`, `config/`, `cli/`, and `tui/`. A missed file breaks detection, registration, or the security response path. The doc lists every file and the exact change each one needs. ## How to use this skill 1. Read `docs/agent-adapter.md` in full. 2. Follow each step in order. Use the wiring table in the doc to change every listed file. 3. Use an existing adapter as your reference. The `agent/gemini/` package is the recommended model for the `settings.json` pattern. 4. Run the verify commands from the doc's final step before you finish. ## Invariants The doc explains these. They break silently if you miss them. 1. Implement `HookConfigPaths()` and return a glob for every file the install step writes. Self-protection guards only these paths. `TestAdapters_InstallWritesOnlyDeclaredHookConfig` fails when a written file has no glob. 2. Implement `Hooks()` with one `events.HookSpec` per hook, including its phase. The decision service reads the phase from it. Regenerate `docs/agent-enforcement-coverage.md` with `GRYPH_UPDATE_DOCS=1 go test ./cli -run TestEnforcementCoverageDoc`. 3. Keep agent knowledge in the adapter package. Do not add agent paths, file names, or command regexes to `aarm/loader` or `aarm/pdp`. The loader derives...