AI triage: move Holmes's GitHub access behind Clearance
This is the first real consumer, and it already works: a broken canary produced a real diagnosis and a real fix PR. The change is small and removes a standing credential, which also takes pressure off a GitHub rate limit that four or more shared tokens have already hit.
Principle honored
Never-persisted credentials, and one GitHub App per consumer as the durable fix for the shared rate-limit bucket (documented in the rate-limit investigation).
What changes
Holmes's GitHub MCP toolset is pointed at Clearance instead of holding github-mcp-token.
Clearance enforces a per-session GitHub API budget; the hot-loop that made ~16k calls an hour is the exact failure this bounds.
The dispatch Job stays exactly as it is: zero RBAC, one HTTP call.
Open questions
Unverified: whether Holmes can call an MCP server that authenticates with a projected service-account token, and forward a task id per request. Check Holmes's MCP config before committing to this design. Its cluster read RBAC stays a documented exception.