docs: record filtered model activity deployment
This commit is contained in:
@@ -23,9 +23,11 @@
|
||||
closes the old EventSource and opens the same session URL again. Failed Resume must not reconnect.
|
||||
- SSE endpoints are intentionally keep-alive. Browser cleanup and one-off probes must explicitly
|
||||
close the EventSource or cancel/abort the response reader after their terminal event.
|
||||
- The Model activity panel is an in-memory chronological projection of the prompt, thinking,
|
||||
assistant output, sanitized tool lifecycle, reviewer gates, status messages, and turn lifecycle.
|
||||
It starts with the local F1 prompt and is deliberately not persisted as chat history.
|
||||
- `activityLog` remains the complete in-memory chronological fold of prompt, thinking, assistant,
|
||||
sanitized tool lifecycle, reviewer gates, status, and turn lifecycle. The left Model activity
|
||||
panel is a strict projection: it renders only prompt, thinking, status, and gate; assistant,
|
||||
tool, lifecycle, and unknown future kinds are hidden. The central transcript and workflow state
|
||||
continue to consume their existing events independently.
|
||||
- Pi tool events may cross the backend/client boundary only as call id, tool name, and
|
||||
`running`/`completed`/`failed` status. Tool updates, arguments, partial/final results, commands,
|
||||
raw output, and raw errors remain server-side.
|
||||
|
||||
Reference in New Issue
Block a user