[BUG] Kimi K2.5 via Moonshot API incorrectly has image support disabled.

[JHawkley]

Problem (one or two sentences)

Kimi K2.5 supports images, but currently has the functionality disabled in its configuration.

A quick test, done by directly editing my local install of Roo, shows the only thing preventing it from working is changing its supportsImages flag to true in packages/types/src/providers/moonshot.ts. The functionality appears to work fine without any other changes and Kimi K2.5 can accurately describe images it is asked to read with this modification.

Context (who is affected and when)

Affects all users who want to integrate images into their workflows using Kimi K2.5 through the Moonshot API.

Reproduction steps

1. Setup a Moonshot provider configured to use Kimi K2.5.
2. Attempt to provide an image through the dedicated button in the prompt field or ask Roo to open and read an image file from the current project.

Expected result

Should allow images to be embedded into the context.

Actual result

No image support.

Variations tried (optional)

No response

App Version

3.47.3

API Provider (optional)

Not Applicable / Other

Model Used (optional)

Kimi K-2.5

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

1. In packages/types/src/providers/moonshot.ts, change the supportsImages flag for the kimi-k2.5 model entry from false to true (line 59).

That's the entire fix -- a single-line change. The issue reporter confirmed the model handles images correctly with this flag enabled, and no other code changes are needed since the rest of the image-handling pipeline already respects this flag.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.