pi provider: decide per event type whether ignored pi events are swallowed, handled or forwarded #97

Problem

pi RPC event types that relay-sessions has no case for fall through translate's default and reach clients as raw_output. Clients such as eve render raw_output as reply text. Known examples: auto_compaction_start and auto_compaction_end, which are bookkeeping, and extension_ui_request, which may need real handling, since pi could be waiting on an answer. relay#48 adds a warning, once per type per session, when this happens.

Acceptance

• Every pi event type pi currently emits is classified as swallowed (bookkeeping), handled (translated to a relay event) or forwarded. Each choice has a test.
• extension_ui_request gets a decision: translate it, answer it, or refuse it visibly. It is never passed through as reply text.

🤖 Generated with Claude Code