Files
goclaw/cmd
yatulandClaude Opus 5 e7e3f25eeb test(teams): pin the teammate streaming contract
Review on #1533 asked for coverage of the behavioural contract rather than
the field assignment, and that is the right call — the PR text arguing a test
would only restate the assignment was wrong, because the contract has two
halves that a refactor could break independently.

The test drives handleTeammateMessage through a real scheduler and asserts
both: the scheduled run requests streaming, and the run is not registered with
the channel manager, so its chunks cannot be routed to a user. It fails with
Stream reverted to false.

The remaining half — a streamed call still yielding the complete final response
— is already covered in internal/agent/loop_pipeline_callbacks_test.go.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-26 16:09:12 +04:00
..
2026-07-15 09:56:43 +07:00
2026-07-31 19:34:40 +07:00
2026-06-12 09:48:01 +07:00