4866a16109
Test / backend-test (pull_request) Has been cancelled
Details
Test / frontend-unit (pull_request) Has been cancelled
Details
Test / api-e2e (pull_request) Has been cancelled
Details
Test / frontend-e2e (pull_request) Has been cancelled
Details
Captures the ReAct streaming contract bug + WS event whitelist governance from PR #13's review fixes. Three intertwined runtime issues documented: 1. P0: final_answer double-accumulated token content (logic_error) 2. P0: _VALID_TEAM_EVENT_TYPES whitelist missing 3 new streaming event types 3. P2: except (RuntimeError, TimeoutError, ConnectionError) too narrow for LLMProviderError/ConfigValidationError in async generator Adds ReAct Streaming Contract entry to CONCEPTS.md — defines the protocol execute_stream() yields (token events with incremental content, then one final_answer event with the concatenated full text). Consumers must pick one accumulation strategy, cannot mix both without doubled output. |
||
|---|---|---|
| .. | ||
| architecture-patterns | ||
| conventions | ||
| integration-issues | ||
| logic-errors | ||
| runtime-errors | ||
| security-issues | ||
| ui-bugs | ||