feat: Add terminal instance selection for @terminal context mention

[roomote]

Summary

This PR attempts to address Issue #10622. Feedback and guidance are welcome.

Problem

When users have multiple terminal tabs open, the @terminal context mention grabs output from all terminals indiscriminately, leading to context pollution and wasted tokens from unrelated terminal sessions.

Solution

This PR adds the ability to select a specific terminal instance when using the @terminal context mention:

1. Terminal sub-selection menu: When selecting @terminal in the context menu, users now see a sub-menu listing all available terminal instances (similar to git commit selection), plus an "All Terminals" option for the previous behavior

2. New mention syntax: Added support for @terminal:name syntax to reference a specific terminal by name (e.g., @terminal:bash, @terminal:zsh)

3. Specific terminal output: When using @terminal:name, only the output from that specific terminal is included in the context

Changes

• packages/types/src/vscode-extension-host.ts: Added TerminalInfo interface and terminalSearchResults/searchTerminals message types
• webview-ui/src/utils/context-mentions.ts: Added Terminal sub-selection in getContextMenuOptions()
• src/core/webview/webviewMessageHandler.ts: Added searchTerminals handler to return terminal instances
• webview-ui/src/components/chat/ChatTextArea.tsx: Added terminal fetching when Terminal type is selected
• src/core/mentions/index.ts: Updated parseMentions and getLatestTerminalOutput to handle @terminal:name syntax

Testing

• TypeScript builds pass
• Existing mention tests pass
• Manual testing recommended for UI interaction

Closes #10622

---

Important

Adds terminal instance selection for @terminal context mention with sub-menu and @terminal:name syntax, updating relevant code and UI components.

• Behavior:
  • Adds terminal instance selection for @terminal context mention with a sub-menu and @terminal:name syntax.
  • Only includes output from specified terminal when using @terminal:name.
• Code Changes:
  • vscode-extension-host.ts: Adds TerminalInfo interface and terminalSearchResults/searchTerminals message types.
  • context-mentions.ts: Updates getContextMenuOptions() to include terminal sub-selection.
  • webviewMessageHandler.ts: Adds searchTerminals handler to return terminal instances.
  • ChatTextArea.tsx: Fetches terminal instances when Terminal type is selected.
• Testing:
  • TypeScript builds pass.
  • Existing mention tests pass.
  • Manual testing recommended for UI interaction.

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

[roomote]

Rooviewer   See task on Roo Cloud

Reviewed the terminal instance selection feature. Found 2 issues to address:

• Duplicate "All Terminals" entry in context menu (webview-ui/src/utils/context-mentions.ts)
• Race condition in terminal focusing with arbitrary 100ms delay (src/core/mentions/index.ts)

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

[roomote]

This filtering will include duplicate entries. The queryItems array already contains a default { type: Terminal, value: "terminal" } entry (added in ChatTextArea.tsx line 297), and then you prepend another "All Terminals" option with the same value. When the terminal sub-menu is displayed, users will see two items that both represent "All Terminals" - one with an explicit label and one that falls back to default rendering.

Consider filtering out the default terminal item before adding the explicit "All Terminals" option:

Suggested change

	if (selectedType === ContextMenuOptionType.Terminal) {
	const terminals = queryItems.filter((item) => item.type === ContextMenuOptionType.Terminal)
	if (selectedType === ContextMenuOptionType.Terminal) {
	const terminals = queryItems.filter(
	(item) => item.type === ContextMenuOptionType.Terminal && item.value !== "terminal"
	)

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

[roomote]

The 100ms delay is an arbitrary heuristic that may not reliably ensure the terminal is focused before selectAll executes. Terminal.show() makes the terminal visible but doesn't guarantee it becomes the active terminal synchronously. On slower machines or busy VS Code instances, this timing may be insufficient, potentially causing content to be copied from the wrong terminal.

Consider using a polling approach with vscode.window.activeTerminal to verify the terminal is actually active, or document this as a known limitation. A more robust pattern might be:

targetTerminal.show()
const maxRetries = 10
for (let i = 0; i < maxRetries; i++) {
	if (vscode.window.activeTerminal === targetTerminal) break
	await new Promise(resolve => setTimeout(resolve, 50))
}

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