fix(sessions): preserve terminal status after agent run completes

[BingqingLyu]

Problem

After a run completes, a session can remain persisted with status: "running" even though endedAt and runtimeMs are already set. This wedges the session: new inbound messages are not accepted and stop/abort commands do not work until the store row is manually edited.

Root cause

persistGatewaySessionLifecycleEvent is called with void (fire-and-forget) in the agent event listener. It enqueues a write to set the terminal status on disk. Immediately after, updateSessionStoreAfterAgentRun enqueues its own write.

The lock queue runs them in order:

1. Lifecycle end handler: reads disk, writes { status: "done", endedAt: X, runtimeMs: Y } ✅
2. updateSessionStoreAfterAgentRun: reads disk (has "done"), but patches from the in-memory sessionStore which was loaded during session initialisation — before the run — and still carries status: "running". mergeSessionEntry(diskState, next) spreads next.status = "running" over the disk's "done", leaving endedAt/runtimeMs intact (they were never in next).

Final persisted state: { status: "running", endedAt: X, runtimeMs: Y } — the exact stuck pattern described in the issue.

Fix

Omit status from the patch passed to mergeSessionEntry inside updateSessionStoreAfterAgentRun. This function is responsible for token/cost/model fields only; lifecycle status is exclusively owned by persistGatewaySessionLifecycleEvent.

Test

Added a regression test in src/commands/agent/session-store.test.ts:

• Disk pre-seeded with { status: "done", endedAt: X, runtimeMs: 1234 } (as if lifecycle end already ran)
• In-memory store has { status: "running" } (stale)
• After updateSessionStoreAfterAgentRun, asserts persisted.status === "done" and endedAt/runtimeMs preserved

Closes openclaw#60250

🤖 Generated with Claude Code