You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix: forward child lifecycle events to handle_event_batch in Primary drain
In drain_family_events, only parent_self_events were passed to
handle_event_batch. convert_lifecycle_events (inside handle_event_batch)
filters by run_id != self_run_id, so it needs child events to inject
lifecycle notifications into OrchestrationEventService for the parent
conversation. Without this, the parent BlocklistAIController never
receives child lifecycle events, causing a regression for local parents
with local or remote children.
Fix: collect child lifecycle events during the drain loop and extend
parent_self_events before the handle_event_batch call in Primary mode.
Co-Authored-By: Oz <oz-agent@warp.dev>
0 commit comments