openclaw - 💡(How to fix) Fix /stop abort leaves streaming card in idle state, blocking subsequent messages (replies=0)

Description

After sending /stop to abort an ongoing agent response, the next message sent to the same chat is silently dropped. The message is received and dispatched to the agent, but the agent is never actually invoked — dispatch completes with replies=0 in under 4 seconds.

Logs

19:14:11 [feishu] received message → dispatched to agent
19:14:15 phase transition rejected (from=idle, to=completed, source=onIdle)
19:14:15 dispatch complete (replies=0, elapsed=3737ms)

The phase transition rejected (from=idle, to=completed is the smoking gun — the streaming card was in an idle state (left over from the /stop abort), and the state machine rejected the transition for the new message.

Key evidence

• No embedded agent logs for the new message — the agent was never called
• Previous /stop shows proper abort: phase transition (from=streaming, to=aborted, source=abortCard)
• After abort, the card state should reset to allow new streams, but it remains stuck in idle
• The fix for the initial message (after gateway restart) works fine — only messages sent after a /stop fail

Environment

• OpenClaw version: v2026.5.24-beta.1 (ea685a7)
• Node: v24.15.0
• Channel: Feishu (WebSocket, streaming cards)

Steps to reproduce

1. Send a message to the agent → agent starts streaming response
2. Send /stop → agent aborts, card transitions to aborted
3. Send another message → message dispatched but agent never runs
4. Dispatch completes in ~3.7s with replies=0
5. Only gateway restart restores normal operation

Expected behavior

After /stop aborts a response, the card/stream state should be fully reset so the next message triggers a fresh agent invocation with a new streaming card.