Skip to content
docs/src/content/docs/contributing/boundaries.md
docs/src/content/docs/extend/server-api.md
docs/src/content/docs/reference/api.md
- Existing similar method in
server/hub.js + route in server/http.js + helper in web/src/lib/api.ts
hub.js — method on the hub, session-scoped, no new global locks unless required
http.js — route → hub; JSON in/out
api.ts — typed-ish helper
- Component or palette — call site
- SSE seq / ring /
chat-stream.ts unless the feature is streaming-related (then stop and re-scope)
- Session open/close path locks “for convenience”
curl or UI proves the route
npm test still passes
- No new HTTP framework