[Chore] Unskip VS Code e2e replay for mutating tools

[roomote]

Opened on behalf of Elliott de Launay. View the task or mention @roomote for follow-up asks.

What problem this solves

Fixes an issue where the remaining mutating VS Code e2e tool suites still stayed skipped after the read-only replay work, which left execute_command, write_to_file, and apply_diff regressions outside the deterministic replay path.

Why this change was made

This slice applies the same deterministic replay approach to the mutating tool suites and adds the model/tool-approval configuration those cases need to exercise the real tool path reliably. It now also validates representative mutating tool-result payloads before replay fixtures hand back canned completions, so drift in the tool output itself still fails replay mode.

User impact

No direct product behavior changes. The mutating VS Code e2e tool suites now run under replay and catch more tool-level regressions before release.

Related PRs

• Read-only tools
• use_mcp_tool
• Subtasks

[roomote]

No actionable issues found. See task

• Wait for TaskCompleted in the write_to_file replay tests so post-write failures still fail the suite.
• Validate the actual mutating tool result payloads in the replay fixtures instead of matching only on toolCallId.
• Fix the recursive list_files replay completion text so it mentions nested/deep/; e2e-mock is failing in Roo Code list_files Tool > Should list files in a directory (recursive).
• Earlier review snapshot: CI completed successfully, including e2e-mock and platform-unit-test (windows-latest).
• e2e-mock and platform-unit-test (windows-latest) finished successfully after the sync-review wait.
• compile, e2e-mock, and platform-unit-test (windows-latest) finished successfully after the sync-review wait.
• Reviewed the read-file.json whitespace-only follow-up in cb244e4; no new issues found.
• Current CI finished successfully, including compile, e2e-mock, and platform-unit-test (windows-latest).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

I see some merge conflicts here. Working on them now...

[roomote]

Addressed the remaining mutating replay-fixture review item in dafa9c9. The replay helpers now validate representative tool-result payloads for apply_diff, execute_command, and write_to_file, and the shared matcher logic is centralized in apps/vscode-e2e/src/fixtures/tool-result.ts.

Revalidated apply-diff.test, execute-command.test, write-to-file.test, pnpm --dir apps/web-roo-code test, and http://127.0.0.1:3000 (200 OK). Browser proof is not applicable here because this is fixture/test coverage work rather than a rendered UI change.

[edelauna]

Increasing test coverage