fix(kimi): preserve current auth and K3 auxiliary contracts

[nicoechaniz]

Summary

• resolve the current Kimi Code CLI OAuth store consistently in runtime and provider discovery
• omit unsupported auxiliary temperature for Kimi, Moonshot, and K3 aliases/endpoints
• keep K3 recognition inside the maintained feat/kimi lane so future integration rebuilds preserve the fix

This replaces #15, whose diff worked on integration main but was not anchored in the canonical Kimi patch lane.

Tests

• scripts/run_tests.sh tests/hermes_cli/test_api_key_providers.py tests/hermes_cli/test_overlay_slug_resolution.py tests/agent/test_auxiliary_client.py tests/agent/test_title_generator.py tests/agent/test_unsupported_temperature_retry.py -q
• During lane replay that suite exposed two K3 regressions; after the lane fix, tests/agent/test_auxiliary_client.py tests/agent/test_moonshot_schema.py passes 364/364.
• The original integration deployment already completed a live K3 title request without a temperature warning.

Deployment

After merge, merge the updated feat/kimi lane into integration main, deploy that exact main to Legion and daimonmatrix, and run the CompAII state sync. K3-256k remains the primary model; auxiliary title/compression remains DeepSeek Flash.