Make `!shell` commands and their output visible to the agent

### Describe the feature or problem you'd like to solve

When I run a command through the !/bang syntax, 9 times out of 10 I want the agent to observe both the command and its output so I don't have to re-paste it.

### Proposed solution

Simply add the command line along with the command's output to the context, just as when the agent ran a command itself. It seems completely oblivious to commands I ran even though the mechanism should be pretty similar.

Nice to have:

- A per-invocation opt-out (e.g. `!!cmd` stays private) for commands with sensitive output.
- A setting for the default (visible vs. private).
- Truncation with "N lines omitted" for very long output, same as existing shell tool.

Why: Right now I either re-run the command through the agent (redundant) or paste the output manually (friction). Bang mode is faster to type but loses context, which defeats the purpose mid-conversation.

### Example prompts or workflows

```
rg 4996 || echo nothing
│
│ nothing
│
└ 1 line
```

As you can see, we already removed the pragmas.

### Additional context

```
❯ rg 4996

❯ Can you see the command and its output that I just ran?

● No — I don't have visibility into commands you run in your own terminal. I only see output from tools I invoke myself (powershell via this session, etc.). If you want me to see it,
paste it or let me re-run it.

❯ But it wasn't terminal. It was here with the ! prefix

● No — !-prefixed commands you run in the CLI UI aren't surfaced to me. I only see what's in the conversation stream (your messages, tool results from my own calls, system
notifications). If you want me to act on that output, paste it.
```

Start by tracing the !/bang command handling and compare it with the existing shell tool's command and output context behavior. Define how a bang command and its output appear in the conversation, then verify the core workflow where the agent can use the result; treat opt-out, default visibility, and truncation as separate decisions because the issue lists them as nice-to-haves.

Escrita pelo modelo de indexação a partir do texto da issue.