fix(vscode): avoid stale queued message state

[marius-kilocode]

Summary

• Fix queued-state detection so a finished assistant update without time.completed does not keep the previous user turn active.
• Add a regression test and patch changeset for prompts sent immediately after a completed response.

Regression source

• Regressed after the Kilo OpenCode v1.3.4 merge: OpenCode v1.3.4 #8798
• Relevant upstream change: refactor(session): effectify session processor anomalyco/opencode#19485
• The processor can emit message.updated with finish: "stop" before cleanup writes time.completed, which made the sidebar treat the previous turn as active and mark the next prompt as queued.

Manual test

1. From packages/kilo-vscode, run bun run extension -- --no-build.
2. Open a sidebar session and send a prompt that finishes normally.
3. After output appears, send another prompt.
4. Confirm the new prompt is active and does not show Queued.
5. While a response is still streaming or using tools, send another prompt.
6. Confirm the second prompt shows Queued until the current turn advances.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)

• .changeset/fix-queued-message-state.md
• packages/kilo-vscode/tests/unit/session-queue.test.ts
• packages/kilo-vscode/webview-ui/src/context/session-queue.ts
• packages/kilo-vscode/webview-ui/src/types/messages.ts

---

_{Reviewed by gpt-5.4-2026-03-05 · 279,593 tokens}