[aofusa]

Description

Adds veil-python (Python, framework profile, emerging, standard mode): an application written with
veil-api 0.10.1, the Python bindings of the veil
server. The HTTP/1.1, HTTP/2, HTTP/3 and WebSocket server is veil's (Rust, epoll readiness reactor in the Linux
wheels); Python runs the handlers. I maintain veil.

• @app.get / @app.post handlers with path and query binding; /baseline11, /baseline2 and /pipeline use
  offload=False (small non-blocking handlers run on the network worker, as in veil-api's production notes).
• /json/{count}?m= returns a dict, serialized to JSON on every request; /delay/{ms} is async def with
  asyncio.sleep on veil's persistent event loop; /echo; /ws is @app.websocket.
• gRPC: the servicer generated by grpcio-tools, registered on veil.grpc.Server(app) with the generated
  add_BenchmarkServiceServicer_to_server (veil serves it; grpcio's server is not used).
• /static/* through app.serve_dir; compression through [api] compression.
• One process with four [[listener]]s from veil.toml.

Completeness: middleware is declared false — veil-api has Depends (before the handler, can answer early) and
native CORS, but no general before-and-after middleware around native routes.

Subscribed tests: the same 22 as veil-api (baseline … echo-ws-limited, including unary-grpc and unary-grpc-tls).

Local validation (./scripts/validate.sh veil-python, veil-api 0.10.1 from PyPI): 113 passed, 0 failed (frag 9/9, WS 7/7, gRPC h2c and TLS, h3, static-tls compression).

🤖 Generated with Claude Code