Ayaan Zaidi 856dbe9017 fix: spawned workers take over the chat you were talking in (#158992) ... * fix(agents): keep spawned workers out of the current conversation Agent-spawned workers (sessions_spawn thread=true, native and ACP) may only bind a new child thread. Channels whose spawn placement is the current conversation (Telegram, Feishu, LINE, generic current-conversation bindings) now reject thread=true instead of handing the user's chat to the worker. Legacy spawn-created bindings on those channels are ignored by the binding service, so the conversation routes to its normal agent again. Discord/Matrix child-thread sessions and defaultSpawnContext are unchanged. * test(telegram): expect parent routing after worker-takeover upgrade * test(agents): refresh prompt snapshots for child-only thread spawns * test(telegram): keep parent-phase checkpoint codes in public upgrade evidence		2026-09-27 11:31:21 +05:30
..
contracts.md
docker.md	fix(e2e): keep older upgrade baselines valid (#159150)	2026-09-26 14:12:24 -07:00
live-workflows.md	improve: profile concurrent Gateway sessions with live OpenAI (#154845)	2026-09-21 13:33:16 +00:00
qa-runners.md	fix: spawned workers take over the chat you were talking in (#158992)	2026-09-27 11:31:21 +05:30
suites.md	fix(test): reap detached children in isolated Vitest runs (#157577)	2026-09-26 19:14:11 -07:00
writing-tests.md	fix(ci): scope PR tests to affected consumers (#156729)	2026-09-24 02:46:40 +00:00