HTTP request limits

The dedicated multiplayer server requires request headers and body to arrive within three seconds after a worker starts reading them. Sending a few bytes at a time does not extend this limit. Slow uploads can fail; retry on a faster connection. Shutdown cancels pending request reads.

The Web dashboard rejects non-string stream_id values in chat cancellation requests with HTTP 400. Invalid JSON types cannot stop the dashboard main loop. Authentication, browser request guards, and license checks still apply.

These are HTTP transport safeguards shared by Web, terminal, and native clients. They do not add commands or change 3D interaction. They do not impose a new total execution limit on tools or streaming responses.