Nitpick: Cap'n Web HTTP and WebSocket should be same endpoint

[kentonv]

computerd publishes Cap'n Web HTTP-batch at /api and Cap'n Web WebSocket at /ws.

Idiomatic Cap'n Web endpoints should place both of these at the same path, preferably /api. There's no need for WebSockets to be served from a different path. The request content (GET with Upgrade vs. POST) unambiguously specifies which the client wants.

(This is a relatively minor thing I noticed while reading the docs. Feel free to ignore me if you prefer.)

[aron-cf]

@kentonv thanks, that makes sense. I'll get that fixed up. Better to align sooner rather than later.