feat: batch consecutive tool calls in chat UI with shared utility

[hannesrudolph]

Closes #11246

After

Summary

Consolidates consecutive list_files, read_file, and file-edit tool ask messages into single grouped UI blocks in the chat — reducing visual clutter when the agent performs multiple similar operations in sequence.

Before: Multiple consecutive list_files calls each render their own "Roo wants to view the top level files in this directory" block with repeated headers. Same for consecutive file edits.

After: They collapse into a single block with all paths listed together.

Changes

New files

• webview-ui/src/utils/batchConsecutive.ts — Generic utility that walks a message array and batches consecutive matches into synthetic messages. Used for all three batching passes (read_file, list_files, file-edits).
• webview-ui/src/utils/__tests__/batchConsecutive.spec.ts — 11 test cases covering empty input, passthrough, batching, mixed sequences, generic typing, immutability, and edge cases.

Modified files

• packages/types/src/vscode-extension-host.ts — Added batchDirs property to ClineSayTool interface
• webview-ui/src/components/chat/ChatView.tsx — Replaced three near-identical batching while-loops (~170 lines) with three batchConsecutive() calls (~70 lines). Added batch button text for listFilesTopLevel/listFilesRecursive and edit-file batches ("Save All"/"Deny All"). Added JSON.parse defense-in-depth in all three synthesizers.
• webview-ui/src/components/chat/ChatRow.tsx — Merged listFilesTopLevel/listFilesRecursive cases; added batch detection for BatchListFilesPermission; normalized language prop to "shellsession"; moved batchDiffs check before switch for all file-edit tool types. Fixed mixed list_files batch icon to default to FolderTree.
• webview-ui/src/components/chat/BatchListFilesPermission.tsx — New component for grouped directory listing UI. Fixed React key to include array index.
• webview-ui/src/components/chat/BatchFilePermission.tsx — Fixed React key to include array index.
• webview-ui/src/components/chat/BatchDiffApproval.tsx — Fixed React key to include array index.
• webview-ui/src/components/chat/__tests__/BatchListFilesPermission.spec.tsx — 5 tests covering rendering, empty state, re-render, container structure, and batch icon fallback.
• webview-ui/src/i18n/locales/en/chat.json — Added wantsToViewMultipleDirectories, dedicated list-batch/edit-batch i18n keys (stop reusing read-batch keys).
• 17 other locale chat.json files — Added wantsToViewMultipleDirectories; removed unused didViewMultipleDirectories

Audit improvements

The following quality fixes were applied during code review:

• Generic batchConsecutive() — Refactored from ClineMessage-specific to a fully generic <T> utility, improving reusability and type safety.
• Edit-batch button text — Added batch-aware "Save All" / "Deny All" button labels for file-edit batches (previously missing).
• Dedicated i18n keys — Added list-batch.* and edit-batch.* i18n key namespaces instead of reusing read-batch keys for different tool types.
• JSON.parse defense-in-depth — Wrapped all three batch synthesizers with try/catch around JSON.parse calls to prevent runtime crashes on malformed message content.
• Mixed list_files batch icon — Fixed icon for batches mixing listFilesTopLevel and listFilesRecursive to default to FolderTree instead of rendering incorrectly.
• +6 new test cases — Added tests for all-match batching, immutability guarantees, spy-based verification, single-directory edge case, and batch icon fallback.

---

Footnote — Minor out-of-scope cleanup:
These changes are unrelated to the batch tool-call feature but were discovered during code review and cleaned up while in the area:

• Trimmed unused recursive/isOutsideWorkspace fields from DirPermissionItem interface in BatchListFilesPermission.tsx (the upstream type in vscode-extension-host.ts retains them)
• Removed 4 pre-existing as any casts in ChatView.tsx — replaced with proper types (ClineMessage, inline window type, direct bracket access, correct debounce API)

---

Design rationale — which tools are batched and why

This PR batches only homogeneous, low-context tool calls where the meaningful information is a file/directory path:

Tool type	Batched?	Reason
list_files	✅ Yes	Output is a directory path — multiple listings collapse naturally into a path list
read_file	✅ Yes	Output is a file path — multiple reads collapse into a file list with per-file approval
File edits (editedExistingFile, appliedDiff, newFileCreated, insertContent, searchAndReplace)	✅ Yes	Output is a diff — multiple edits collapse into expandable per-file diffs
codebaseSearch	❌ No	Each search has a unique query returning 20–30 ranked results with scores and code snippets. Batching would lose the query→result mapping.
searchFiles	❌ No	Each regex search returns different result counts and patterns. Per-query context is essential.
execute_command	❌ No	Commands have different risk profiles. Users must see and approve each one individually (security concern).

Guiding principle: Batch when the per-call output is a simple path or diff. Don't batch when each result has rich, query-specific content that would be lost in a combined view.

[roomote]

Oroocle   See task

The latest commit (c15377e) adds list-batch and edit-batch i18n translations across all 17 non-English locale files. Structure is consistent with the English source and all locales properly differentiate "Approve All" vs "Save All" labels. No new issues found.

• Consolidate the duplicate batch-handling blocks in ChatRow.tsx for listFilesTopLevel and listFilesRecursive into a single combined case

Previous reviews

• 946ab9f: Review #1
• 9ffc778: Review #2
• 3034b55: Review #3
• 2e02d04: Review #4
• 51eb54d: Review #5
• 0160847: Review #6
• db94d81: Review #7
• 056465f: Review #8

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