Release v2026.8.3 · hex/claude-council

What's Changed

The Kimi API provider answers again. It sent temperature: 0.7 to match the other providers, and Moonshot rejects every value but 1 across its model line, so every Kimi API query failed outright with "invalid temperature: only 1 is allowed for this model". Anyone with KIMI_API_KEY set has had a dead provider in the council since Kimi was added. check-status reported it connected throughout, because that probe is a /models GET rather than a completion.
The documented Kimi model list named ids that not every account can reach. Moonshot closed the moonshot-v1 series, its -vision-preview variants and kimi-k2.5 to newly registered accounts ahead of a 2026-08-31 sunset, so a recent key gets 404 for ids the vendor still documents while an older key does not. kimi-latest was discontinued outright on 2026-01-28. The comment now points at GET /v1/models, which answers this per key, instead of naming a set that is correct for one account and wrong for the next.

Five gated tests check that the real endpoints accept what each provider sends. The hermetic tests drive a fake curl, so they assert the endpoint, the key staying off argv and the prompt reaching the body file, and none of them can assert the endpoint accepts any of it. The Kimi payload passed every one while failing every real call. Run them with COUNCIL_E2E=1; they skip by default, skip again when a key is absent, and never run in CI.
Test inventory corrected in TESTING.md, which also documents COUNCIL_E2E. That gate gated three CLI tests already without appearing in any documentation.

Full Changelog: v2026.8.2...v2026.8.3