hooks: unknown-tool live fallback behavior not E2E validated

[sharkich]

Unit test covers unknown fixture throw (hooks/tests/fixtures/unknown-ide-input.json). No live capture of an actual unknown tool event from a real IDE. Gap for extended QA pass. AC: capture live stdin from an unsupported/unknown tool invocation and run normalize() to verify error handling path.

[github-actions]

Rosetta Triage

Classification: enhancement
Priority assessment: Medium (P3) — this is a test coverage gap, not a production defect. The happy-path and fixture-based error paths are already covered by unit tests; the missing piece is a live end-to-end capture from a real unsupported/unknown IDE tool invocation. The acceptance criteria are clear and the scope is well-defined.

The issue is actionable as stated. Suggested next steps:

• Capture live stdin from an unsupported/unknown tool invocation against a running hooks process
• Pipe the captured event through normalize() and assert the error-handling path behaves as expected
• Add the captured fixture to hooks/tests/fixtures/ for regression coverage

Automated triage by Rosetta agent