fix: prevent git protocol errors from triggering naughty list

Change protocol error detection to only match WebSocket-specific errors
(websocket, invalid frame) instead of generic 'protocol' keyword which
was incorrectly catching transient git protocol errors.

Git protocol errors like 'fatal: protocol error: bad line length' are
transient network issues that should use backoff/retry, not permanent
naughty list blocking. Only WebSocket/Nostr protocol violations indicate
persistent infrastructure problems.

Fixes production false positive:
- relay.ngit.dev: git protocol error + remote warning misclassified

Add production test cases for git protocol errors and warning combinations.

0 files changed, 0 insertions, 0 deletions