RFC 9112 §6.1 forbids `Transfer-Encoding` on a 204, which zttp refuses to serialize.

Test that a peer that never echoes the close frame cannot keep the connection. RFC 6455 7.1.1 lets the server close the connection once the reply

Test that closing resumes paused reads, so the peer close frame can be received.

The ASGI callable should call the `websocket.close` event. If it doesn't, the server should still send a close frame to the client.

Test that a server close leaves the transport open until the peer echoes it. Closing it right away makes the peer's reply (RFC 6455 5.5.1) land o

Test that losing the connection stops waiting for the peer close frame.

Test that connection loss releases a send blocked on backpressure.

By default, context set outside the ASGI task is visible inside it.

Test that a peer close frame is processed even when preceded by data in the same read.

Test that a data frame crossing the server close cannot block the peer close frame.

Calling `default_ssl_context_factory()` without `ssl_certfile` raises a clear error.

Test that one can load environment variables using an env file.

A glob include inside an excluded directory is not watched. Pins the branch directly: the reload tests that exercise it through real file wat

Stream non-FIN fragments past `ws_max_size` - the server must close with 1009.

Server reassembles a fragmented message and delivers it to the app intact.

A frame arriving after the close handshake, e.g. a pong the client sent while the server's close reply was in flight, must not crash the protocol