Module http/server

Minimal HTTP/1.1 server on TcpListener (plans/archive/STD_API_AUDIT.md §7 P1).

One connection at a time, one request per connection (Connection: close is added to every response) — the shape a CLI, a test fixture or a local tool needs; it shares its wire code (std/http/wire.yo) with the client, so request bodies may be Content-Length or chunked.

{ HttpServer, HttpResponse } :: import "std/http";
server := io.await(HttpServer.bind(SocketAddr.loopback(u16(8080)), io), e);
io.await(server.serve((req) -> HttpResponse.with_status(StatusCode.OK()).with_body(`hi ${req.path}`), io), e);

serve runs until stop() is called (checked after each connection) — from another task, or from the handler itself. serve_once handles exactly one connection, which is what a test wants.

A client's mistake never takes the server down: a request that does not parse gets 400, one that exceeds max_request_bytes gets 413, one with broken framing (Content-Length that is not a number, malformed chunking) gets 400 — and serve goes on to the next connection. An I/O failure on the accepted socket itself still propagates out of serve.

Stability

unstable — the SHAPE (one connection at a time, one request per connection, Connection: close on every response) is expected to change when a connection loop / keep-alive lands; bind, local_addr, with_max_request_bytes, serve, serve_once, stop and close are intended to keep their names and meanings.