trimwire

Use when the user asks — inside a Claude Code session — how much context trimwire is saving, for cache/token stats, to find or inspect a past session, to preview what pruning would do, to benchmark/share a summarizer model, to opt in/out of the community dashboard, OR when something trimwire did looks wrong (content went missing, a re-read loop, a summary looks fabricated) and you want to explain it / file a report. It shells the local `trimwire` CLI (safe, local, content-free) and explains the output. Triggers like "how much is trimwire saving?", "is trimwire working?", "trimwire stats", "what would pruning trim here?", "find my session from earlier", "share my benchmark", "opt in to the dashboard", "something trimwire did looks wrong", "report a trimwire bug".

Workflow guidance for implementing the trimwire gateway. Covers request-path buffering, response-path SSE streaming, pairing-index invariants, strategy module pattern, ledger conventions, and the cache-prefix-hash requirement. Invoke when working on src/proxy/gateway.rs, src/strategies/*, src/pairing.rs, src/proxy/upstream.rs, src/proxy/proxy_stream.rs, or src/ledger.rs.