Repository navigation
0.1.8 Beta6: Define progressive Chat and Collaboration V2 streaming #254
Description
This was generated by AI during triage and updated by the approved Beta6 scope decision.
Parent
What to build
Define and verify the progressive Chat-to-Responses streaming contract consumed by the three Beta6 Ollama Chat tracer bullets #285, #286, and #396, including standard tools and the complete Collaboration V2 lifecycle.
The real CLI must receive incremental text and V2 tool lifecycle events with bounded buffering, exact identity preservation, backpressure, and stable terminal/error classification.
Acceptance criteria
- 0.1.8 Beta6: Complete the GLM-5.2 Ollama Chat and V2 CLI path #285, 0.1.8 Beta6: Complete the K2.7 Code Ollama Chat and V2 CLI path #286, and 0.1.8 Beta6: Complete the DeepSeek V4 Flash 0731 Chat CLI path #396 stream incrementally through the real CLI rather than buffering the complete upstream response.
- Text, standard function calls/results, all six V2 calls/results, task/call/item identity, terminal ordering, and errors survive conversion.
- V2 argument deltas are assembled before validation and emit the exact Responses added/delta/done sequence expected by the client.
- Buffering and backpressure are bounded.
- Cancellation and upstream failure stop work without duplicate terminal events or replay after side effects.
- A conversion failure after stream start emits exactly one standard
response.failedterminal. - No hidden Responses/Official fallback occurs.
- Other Chat capabilities remain within the documented Beta6 ceiling.
Activity
[-]0.1.8 Beta2: Stream Chat upstreams incrementally through Responses SSE[/-][+]0.1.8 Beta4: Define the progressive Chat streaming contract[/+]1 remaining item
[-]0.1.8 Beta4: Define the progressive Chat streaming contract[/-][+]0.1.8 Beta5: Define the progressive Chat streaming contract[/+][-]0.1.8 Beta5: Define the progressive Chat streaming contract[/-][+]0.1.8 Beta6: Define the progressive Chat streaming contract[/+][-]0.1.8 Beta6: Define the progressive Chat streaming contract[/-][+]0.1.8 Beta6: Define progressive Chat and Collaboration V2 streaming[/+]NOirBRight commentedon Aug 19, 2026
Campaign rewrite from #441: this streaming contract is now blocked only by #66. Provider qualification tickets consume it; they do not block it.
NOirBRight commentedon Aug 19, 2026
Streaming/terminal dispositions are in the #66 matrix (stream.text.delta, stream.function.delta, stream.terminal.*, cancellation). Remaining #254 work is the progressive-stream state machine on top of that matrix after #442, not a second event table.
NOirBRight commentedon Aug 19, 2026
Completed by the #395 streaming state-machine evidence plus final authenticated Provider qualification.
response.failedafter stream commit.docs/evidence/authenticated-provider/chat/summary.jsonatc82baad, bound to source73e4ed3. GLM/Kimi/DeepSeek each passed real CLI progressive streaming (21/10/11 qualifying streams), exact standard/custom lifecycle identity, independently qualified six-tool V2 phases, child delivery, parent completion, same-Home restart, and Cross-Home rejection.No hidden Responses/Official/Provider/model fallback was introduced.