+4 -3

README.md

Reviewed

··· 20 20 - `httpz` is the HTTP/1.1 server boundary. ZDS should consume it directly from 21 21 Tangled, not vendor it. HTTP server behavior should stay local to ZDS unless 22 22 it is a focused compatibility fix or improvement for `httpz` itself. 23 23 - - `zat` and `httpz` both rely on Karl Seguin's `websocket.zig`. Keep the graph 24 24 - on one websocket implementation; fix the upstream package we control rather 25 25 - than copying it into this repo. 23 23 + - `zat` and `httpz` both rely on the canonical first-party 24 24 + [`websocket.zig`](https://tangled.org/zzstoatzz.io/websocket.zig). Keep the 25 25 + graph on one websocket implementation; fix the upstream package we control 26 26 + rather than copying it into this repo. 26 27 - Vendoring is a last resort for short-lived debugging only. Do not leave 27 28 `vendor/` as the dependency strategy. 28 29

+3 -3

docs/development.md

Reviewed

··· 49 49 from Tangled and send focused fixes upstream when its HTTP or websocket behavior 50 50 needs to change. 51 51 52 52 - Keep the websocket graph singular. `httpz` uses Karl Seguin's `websocket.zig`, 53 53 - and `zat` should use the same package so ZDS does not pull two websocket 54 54 - implementations into one build. 52 52 + Keep the websocket graph singular. `httpz` and `zat` should both use the 53 53 + canonical first-party `zzstoatzz.io/websocket.zig` package so ZDS does not pull 54 54 + two websocket implementations into one build. 55 55 56 56 Vendoring is only acceptable as a temporary local debugging move. Before a 57 57 change is considered ready, remove `vendor/`, express dependencies in