fix(kosong): correct type inference when enum/const contradicts expli…

[logic10492]

 ## Related Issue

 N/A — no prior issue opened for this bug.

 ## Problem

 When a tool JSON schema explicitly declares a `type` that contradicts the actual values in `enum` or `const` (e.g. `type: 'object'` with `enum: ['move', 'copy']`), `normalizeKimiToolSchema` previously only  inferred the type when it was missing. It did **not** correct a mismatched explicit type, leaving an invalid schema that could propagate downstream.

 ## What changed

 Updated `normalizeProperty` in `packages/kosong/src/providers/kimi-schema.ts` so that when `enum` or `const` is present, the function now:

 1. Infers the type from the enum/const values if `type` is absent (existing behavior preserved).
 2. Corrects the `type` if it is already present but contradicts the inferred type from enum/const values.

 Added a test case in `kimi-schema.test.ts` covering both `enum` and `const` mismatch scenarios.

 ## Checklist

 - [x] I have read the [CONTRIBUTING](https://github.com/MoonshotAI/kimi-code/blob/main/CONTRIBUTING.md) document.
 - [x] I have explained the problem above (no linked issue).
 - [x] I have added tests that prove my feature works.
 - [x] Ran `gen-changesets` skill — `.changeset/fix-schema-enum-type-inference.md` added.
 - [x] Ran `gen-docs` skill, or this PR needs no doc update. <!-- needs no doc update -->

[changeset-bot]

🦋 Changeset detected

Latest commit: 06d9255

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

[logic10492]

I first encountered this issue while integrating with xcodebuildmcp. Although the upstream project has since addressed it on their end, I believe applying this
fix at the framework level improves overall compatibility
and prevents similar issues for other integrations.

[pkg-pr-new]

pnpm dlx https://pkg.pr.new/@moonshot-ai/kimi-code@06d9255

npx https://pkg.pr.new/@moonshot-ai/kimi-code@06d9255

commit: 06d9255

[7Sageer]

Thanks for the PR — tests and changeset included.

Our take: { type: 'object', enum: ['move', 'copy'] } is a bug on the MCP server's side and should be fixed there. We'd rather have providers conform to the spec than guess which of two contradictory fields the author meant and overwrite it — that risks guessing wrong and hides the real bug.

normalizeKimiToolSchema only fills in a missing type (which Moonshot requires); rewriting a type the server explicitly declared is a different thing we'd rather not do.

It also regresses valid input — calling inferTypeFromValues on already-typed nodes throws on schemas that used to pass through:

{ type: 'string', enum: ['low', 'medium', null] }  // valid nullable enum
// before: unchanged;  after: throws "Mixed JSON Schema enum or const types..."

Closing for now — if you have a concrete case where a contradictory type actually breaks a request, share it and we'll revisit. Thanks again!