fix(terminal): don't hardcode 'Linux environment' in tool description (#7672)

[iacker]

Summary

Fixes #7672. The terminal tool description opened with "Execute shell commands on a Linux environment", which is misleading for users running locally on Windows/macOS or against a non-Linux configured backend.

Fix

Reword the first sentence to frame the environment as configured — local machine, Docker container, or cloud sandbox depending on setup — without hardcoding Linux. Minimal one-line change to the description string; the rest of the prompt (read_file/search_files/patch guidance, the persistence contract) is untouched.

-Execute shell commands on a Linux environment. Filesystem, current working directory, ...
+Execute shell commands in the configured execution environment (local machine, Docker container, or cloud sandbox depending on setup — not necessarily Linux). Filesystem, current working directory, ...

Tests

Adds tests/tools/test_terminal_tool_description.py with invariant-style assertions (not a snapshot freeze):

• description no longer contains "Linux environment"
• it names the real configured options (local machine / Docker container)
• the "persist between calls" persistence contract survives

3 passed in 1.09s

Note

Rebased reimplementation of #23242 onto current main (the base description string had since changed, so the old branch no longer applied cleanly). #23242 will be closed in favor of this one.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #7667 — both reword TERMINAL_TOOL_DESCRIPTION in tools/terminal_tool.py from "Execute shell commands on a Linux environment" to a configured-environment phrasing for the same issue #7672 (#7667 is the earliest open competing fix; the canonically-titled #8364 is closed).

[iacker]

Re the duplicate flag: agreed #7667 targets the same issue (#7672) and is earliest — happy to defer if it lands. Two factual notes for whoever triages the cluster:

• Fix misleading terminal tool description for Windows users #7667 was last updated 2026-04-29 and its merge state is currently unknown; the TERMINAL_TOOL_DESCRIPTION base string has changed on main since then (that drift is what killed my own earlier attempt fix(terminal): clarify configured execution environment #23242/fix(terminal): clarify configured execution environment #8364).
• This PR is a minimal re-fix against current main (single string + an invariant-style test that doesn't freeze the exact wording), all checks green.

Whichever vehicle maintainers prefer — the point is just that #7672 is fixable today with a green, conflict-free diff.