feat: add support for image file @mentions

[hannesrudolph]

Summary

Add support for resolving image file @mentions into inline images, and align edit-dialog test expectations with current behavior (empty-array images for submits; undefined for edit-dialog payload).

Changes

• Add image mention resolver and wire it into the webview message flow.
• Add unit + integration tests for image mention resolution.
• Fix edit-dialog related tests to match actual images payload shape.

---

Important

Adds support for resolving image file mentions into inline images and updates related tests and message handling.

• Behavior:
  • Adds resolveImageMentions function in resolveImageMentions.ts to convert image file mentions into inline images.
  • Integrates resolveImageMentions into webviewMessageHandler.ts to handle image mentions in messages.
  • Updates editMessageConfirm and askResponse cases in webviewMessageHandler.ts to use resolved images.
• Tests:
  • Adds unit tests in resolveImageMentions.spec.ts for various image formats and scenarios.
  • Adds integration tests in webviewMessageHandler.imageMentions.integration.spec.ts for newTask and askResponse message types.
  • Updates existing tests in ClineProvider.spec.ts and webviewMessageHandler.edit.spec.ts to align with new image payload expectations.
• Misc:
  • Updates getFileOrFolderContent in index.ts to omit binary files from text context.

^{This description was created by for f2d1554. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Oroocle   See task on Roo Cloud

Re-review complete. No new issues found in the latest commit; remaining follow-ups below.

• Enforce image size limits when resolving image @mentions (avoid large base64 payloads / memory spikes)
• Ensure .rooignore enforcement is consistent for image @mentions even when no current task exists (newTask path)
• Ensure image @mentions respect model image capability (avoid resolving/encoding for non-vision models)

Previous reviews

• 24b1f6e: Review #1
• bc49d92: Review #2

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

resolveIncomingImages uses the task's rooIgnoreController but falls back to provider.cwd when there is no current task. That means image mentions in the initial newTask message do not get .rooignore enforcement (unless provider.getCurrentTask() already exists), which is a behavior difference from text mention expansion. Consider using a provider-level RooIgnoreController for the fallback path as well.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[roomote]

supportsImages defaults to true here, so if a caller forgets to pass the real model capability this will still read and base64-encode image mentions for non-vision models (extra memory + large payloads). Consider deriving/passing supportsImages from the active model info (or defaulting this to false so callers must opt-in explicitly).

_{Fix it with Roo Code or mention @roomote and request a fix.}

[daniel-lxs]

A couple spots where we could reuse existing helpers from imageHelpers.ts:

1. isSupportedImageExtension() is identical to the already-exported isSupportedImageFormat() - can just import that instead of defining a local version.

2. The base64/data URL logic:

const buffer = await fs.readFile(absPath)
const base64 = buffer.toString("base64")
newImages.push(`data:${mimeType};base64,${base64}`)

readImageAsDataUrlWithBuffer() already does exactly this and is exported. Could simplify to:

const { dataUrl } = await readImageAsDataUrlWithBuffer(absPath)
newImages.push(dataUrl)

Minor stuff, but keeps things aligned with existing patterns.

[ellipsis-dev]

The constant SUPPORTED_IMAGE_FORMATS (lines 5–17) is declared but never used. Consider removing it to keep the test file clean.