m0serve: realtime Django and Flask without the usual stack

Field notes

The documented integration keeps authorization in the ordinary synchronous view, then uses M0-Hold and M0-Channel response headers to hand the connection to m0serve. A separate view, command, or cron job publishes to the named channel through m0pub.publish. The project presents both WSGI and ASGI modes, and its evidence trail includes PEP 3333 checks, an ASGI validator, RFC 6455 probes, and CI-driven Django, Flask, and FastHTML smoke tests.