[Bug] After compaction, queued messages do not fire and cannot be edited/deleted

[adam820]

Description

After usage of the /compact command, messages queued during the compaction phase do not auto-start after the compaction is complete, remaining in the queue.

Environment

• OS: Fedora Linux 44 (Workstation Edition)
• Node version: v26.7.0
• Nanocoder version: 1.30.0
• Provider: Ollama 0.33.0
• Model: laguna-xs-2.1:q8_0 (not related; happens with other models)

Steps to Reproduce

1. Run /compact
2. While compaction is running, add a new prompt and hit "Enter" so it goes into the queue
3. Wait for compact to finish and observe the queued message being stuck

Expected Behavior

The first message in the queue would start to run (e.g. a request in plan mode, 'Your next task is...', etc.

Actual Behavior

The compaction finishes, prompt returns and can be typed in, but queued messages stay in the queue; the method of selecting them for edit/delete also no longer works (down does nothing, up rolls back through old prompts). In order to get them to work, you have to provide a new prompt, cancel it, then select the next message to start it going.

Logs/Screenshots

Quick "write me a an overview of 6502 emulation" -> compact -> queue "Write me lorem ipsum" -> Prompt doesn't fire; hitting down arrow does nothing, hitting up arrow shows me last message (that I typed to queue).

Additional Context

• I have searched existing issues to ensure this is not a duplicate
• I can reproduce this issue consistently (happens all the time)
• This issue occurs with the latest version of nanocoder

[mikemikimike]

I opened PR #1069 to fix this.

The issue was in the completion lifecycle: queued prompts were drained when an LLM conversation finished, but slash commands such as /compact only marked the conversation complete and never invoked the queue drain. The PR forwards slash-command completion through the existing app lifecycle so queued prompts resume after compaction, while preserving the existing FIFO queue and edit/delete behavior.

It includes a regression test for the completion state transition and callback, plus a patch changeset. Focused tests and type/lint/format checks pass locally; the full suite has unrelated Windows/network/platform baseline failures and timeouts documented in the PR.

[awhite0030]

Picking this up - a fix will follow shortly.

[mikemikimike]

I opened a clean replacement PR, #1210, addressing the review feedback from #1069.

The fix drains queued prompts only after the app is fully idle, keeps the plan-review modal and pending plan transition protected, removes the duplicate slash-retry completion signal, and restores idle queue navigation/edit/delete behavior. It also adds regression coverage for these cases.

All GitHub CI checks for PR #1210 are passing, including unit tests and coverage, type checks, format/lint checks, build, audit, CodeQL, Semgrep, and the automated review.