Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@internal/agent/bash.go`:
- Around line 138-189: The current executeWithBash (and the similar command
execution block later in this file) uses bytes.Buffer for cmd.Stdout/cmd.Stderr
which can grow unbounded; replace those buffers with a capped writer/ring buffer
that implements io.Writer and enforces a configurable maxOutputLength (use the
existing maxOutputLength constant), stop accepting bytes once the cap is reached
and record an overflow marker (e.g., "...[truncated]" or similar) so callers
know output was truncated; wire cmd.Stdout and cmd.Stderr to this capped writer,
and when returning commandRunResult ensure you return the capped writer's
contents via its String() method (preserving existing stdout/stderr semantics)
and preserve error handling behavior.

In `@internal/agent/system_prompt.txt`:
- Around line 101-105: The example uses $TMPFILE but never initializes it;
update the snippet or surrounding text so TMPFILE is created before use (e.g.,
via a host-appropriate temp creation like mktemp) or explicitly label the block
as pseudocode that assumes a temp path exists; reference the symbols $TMPFILE
and ${CONTENT} in the guidance so the reader knows to create/obtain TMPFILE
before running the shown printf and some-cli-tool < "$TMPFILE" sequence.

---

Nitpick comments:
In `@internal/agent/bash_test.go`:
- Around line 215-311: Add a test case in TestExecuteCommand_InterpreterFallback
that exercises a PATH-installed CLI to lock the fallback contract: create a temp
dir, write a small executable helper script that prints a distinct marker, chmod
it executable, prepend that dir to PATH in the environment used by
runCommandWithFinder, then call runCommandWithFinder (same signature used
elsewhere in this file) with the helper script name as the command and
noBashPath so the interpreter fallback must invoke the PATH binary; assert the
result is not an error and contains the marker. Ensure you reference
TestExecuteCommand_InterpreterFallback, runCommandWithFinder and noBashPath when
locating where to add the case.

In `@internal/agent/system_prompt.txt`:
- Line 97: The system prompt wording incorrectly calls the fallback a “built-in
POSIX shell interpreter”; update the sentence to reflect the actual fallback
syntax by using phrasing like “built-in shell interpreter” or “bash-compatible
shell interpreter” to match how internal/agent/bash.go parses the fallback with
syntax.LangBash and how internal/agent/bash_test.go validates [[ ... ]]; replace
the phrase and adjust the example list if needed to avoid implying strict
POSIX-only behavior.