fix: set Kimi temperature when thinking is disabled

[ktwu01]

Related Issue

Fixes #686

Problem

When Kimi thinking is disabled, the provider sends thinking: { type: "disabled" } but does not set a temperature unless one was provided through generation kwargs. The managed Kimi coding model rejects thinking-disabled requests unless the request uses temperature: 0.6.

What changed

• Set temperature: 0.6 on Kimi requests when thinking.type is disabled and no explicit temperature is already present.
• Preserve explicit temperature values from caller configuration.
• Added coverage for the default and explicit-temperature paths in the existing Kimi provider test file.
• Added a changeset for @moonshot-ai/kosong and the CLI bundle.

Validation

• pnpm --filter @moonshot-ai/kosong exec vitest run test/kimi.test.ts
• pnpm --filter @moonshot-ai/kosong typecheck
• pnpm --filter @moonshot-ai/kimi-code typecheck
• pnpm exec oxlint --type-aware packages/kosong/src/providers/kimi.ts packages/kosong/test/kimi.test.ts
• Read-only staged diff audit for internal identifiers and secrets: clean

Checklist

• I have read the CONTRIBUTING document.
• I have linked a related issue, or explained the problem above.
• I have added tests that prove my feature works.
• Ran gen-changesets skill, or this PR needs no changeset.
• Ran gen-docs skill, or this PR needs no doc update.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4102ac2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@moonshot-ai/kosong	Patch
@moonshot-ai/kimi-code	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR