logging: silence tungstenite/tokio_tungstenite DEBUG noise too

[ajslater]

Summary

The earlier _granian filter (#704) didn't actually silence the WebSocket close-frame DEBUG noise users were still seeing. Those messages originate from the tungstenite / tokio_tungstenite crates that Granian uses for its WS layer, not from _granian itself.

DEBUG | Received close frame: Some(CloseFrame { code: Normal, … })
DEBUG | Replying to close with Frame { … Control(Close) … }
DEBUG | websocket start_send error: WebSocket protocol error: Sending after closing is not allowed

pyo3-log routes Rust tracing targets to Python loggers, mapping :: → ., so e.g. tungstenite::protocol arrives as the Python logger tungstenite.protocol. Filtering the bare crate name applies hierarchically to all submodules.

Test plan

• make lint-python clean
• make ty clean
• pytest tests/ clean (26 passed)
• Apply the dictConfig in a Python REPL and confirm:
  • tungstenite.protocol effective level → INFO, isEnabledFor(DEBUG) → False
  • tokio_tungstenite.compat effective level → INFO, isEnabledFor(DEBUG) → False
  • _granian.asgi.io effective level → INFO (existing filter still works)
  • root effective level → DEBUG (codex code unaffected)
• Verify in production Docker that the close-frame DEBUG lines no longer appear

Note

make lint (the wrapping script, not the underlying tools) errors on nginx/http.d with "Cannot process specified file: it's ignored" — reproducible without my changes, so unrelated. Worth fixing separately.

🤖 Generated with Claude Code