Live trace of one execution (SSE)
Tails the engine’s append-only Journal for the execution: emits every entry, closing after the terminal run_finished entry. Since runs are dispatched SYNCHRONOUSLY (plane.rider.run is awaited before the run_ref is written), by the time a client can open this stream the journal is already complete — it replays once and closes, rather than ticking live.
承認
The dashboard's signed, HttpOnly session cookie (packages/service/src/auth.ts): base64url(payload).base64url(hmac-sha256), absolute 30-day lifetime, SameSite=Lax, Secure on any TLS deployment. Minted by POST /api/auth/signup or POST /api/auth/login (or, outside production, auto-provisioned by GET /api/session). Because it is HttpOnly, it cannot be read or attached by a browser-based API-reference "Try it" panel across origins — exercise these routes with a real logged-in browser session or a cookie-jar HTTP client.
パスパラメータ
The run_ref id, or the engine run_id.
レスポンス
An event: <JournalEntry.event> / data: <JSON JournalEntry> stream.
The response is of type string.