stream_job_events

Stream job progress as Server-Sent Events. Cost class: fast.

Each frame is a :class:~ndi_service.app.platform_api.results.JobEvent serialised as data: <json>\n\n with a monotonic id: <sequence>. Frames are emitted by polling the job row — the row is the event source, so a frame appears whenever status or progress changes and the stream closes once the job is terminal (or after the same ceiling as the inline wait, for a job nothing is advancing).

REST and CLI only. MCP has no streaming shape; an MCP agent polls get_job instead.

Last-Event-ID offsets the sequence numbering so a reconnecting client keeps a monotonic id; the current state is always re-emitted as the first frame, because there is no event log to replay from.