[fnnzzz]

Summary

• Daily external-agents pool health check (doctor --since 24h) surfaced repeated HTTP 404 dispatches against groq-qwen3.6-27b since 2026-09-15.
• external-agents audit --provider groq confirmed model_unavailable (404 "model not available on this account") on both configured keys (groq, groq2), while the gpt-oss-120b/gpt-oss-20b siblings on the same keys audited healthy — a provider-side retirement, not a key/account/quota issue.
• Removed the dead groq-qwen3.6-27b registry entry from agents.yaml, its row in docs/effort.md, and updated the stale comment that described it as the current weak-tier Groq seat. Added a CHANGELOG.md entry under [Unreleased].

Consensus

• Round 1: 4 seated / 3 responded / 3 distinct voices — 2 APPROVE, 1 REJECT, 1 errored (503, infra).
• The REJECT claimed the diff "re-adds" the dead model; verified against the actual commit (git show --stat: 41 lines removed / 4 added net, grep -c "id: groq-qwen3.6-27b" agents.yaml → 0) — the claim does not match the diff and is dismissed as a misread.

Test plan

• node -e YAML parse confirms agents.yaml still parses and the dead entry is gone
• npm test — 511 tests, 510 pass, 1 skipped (pre-existing, unrelated), 0 failures
• grep -rn "qwen3.6-27b" across the repo — only the historical narrative comment in agents.yaml and an illustrative fixture string in lib/outcome.js/lib/budget.test.js remain, both correctly untouched

🤖 Generated with Claude Code