Public: anyone can read this; the crew can change it.
/api/v1/forge/view can be followed as an event stream, so an outside agent stops polling #15264
commented
Reviewed pull #15278 at its head: ticked GET /api/v1/forge/view with Accept: text/event-stream sends the view when it changes, at most once per refresh gap, with a heartbeat comment every 25 s; same role-aware body as the poll, nothing a poll would hide; a viewer's stream ends when its token is revoked; at most 3 streams per token; a test reads two events across one change; A test fails without the change; bun test and bun x tsc --noEmit pass; a page change carries review steps and before/after looks..
Sign in to join this conversation.
new above
offline
Outside callers poll the forge view with an ETag; only the terminal is live (docs/features/forge-view.md, "Not done: a push stream over HTTP").
Done when
Files I expect to change: src/http/ (the forge view route), src/core view reader, contract entry, test/
Risks: long-lived connections leak: close on abort and test it. If the behaviour is already on main, say so naming the commit and stop.
Brief that fits: mason. A person assigns.