docs: document compound command matching, update changelog with filter fixes

Author: bug-ops

CHANGELOG.md

@@ -6,6 +6,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+### Fixed
+- Filter metrics not appearing in TUI Resources panel when using native tool_use providers (#480)
+- Output filter matchers not matching compound shell commands like `cd /path && cargo test 2>&1 | tail` (#481)
+- Duplicate `ToolEvent::Completed` emission in shell executor before filtering was applied (#480)
+
 ### Added
 - Syntax-highlighted diff view for write/edit tool output in TUI (#451)
   - Diff rendering with green/red backgrounds for added/removed lines

docs/src/guide/tools.md

@@ -115,6 +115,10 @@ Stale overflow files older than 24 hours are cleaned up automatically on startup
 
 Before tool output reaches the LLM context, it passes through a command-aware filter pipeline that strips noise and reduces token consumption. Filters are matched by command pattern and composed in sequence.
 
+### Compound Command Matching
+
+LLMs often generate compound shell expressions like `cd /path && cargo test 2>&1 | tail -80`. Filter matchers automatically extract the last command segment after `&&` or `;` separators and strip trailing pipes and redirections before matching. This means `cd /Users/me/project && cargo clippy --workspace -- -D warnings 2>&1` correctly matches the `ClippyFilter` — no special configuration needed.
+
 ### Built-in Filters
 
 | Filter | Matches | What it removes |