0846708c5a
Drop the once-per-method dedup and its per-runner state: the client now warns on every unbound notification (registering a binding, even a no-op one, is the silence), and server-side inbound drops return to debug since the peer is an arbitrary client and warning on its input floods the log. Revert the ClientSession.send_notification widening: the 2026-07-28 transports do not agree on client-to-server custom notifications yet, so the closed union stays the accurate type. Carve notifications/cancelled and listen-owned acks out of the message_handler catch-all claim, add the imports the notification example was missing, and note that a json_response answer has no stream to carry request-scoped notifications.