Changing a blocked task to In Progress can immediately move it to Backlog

[kylecarbonneau]

Opening as an issue instead of a PR, since I’m not sure if this is intentional or a bug. Expected behavior was that manually marking as In Progress would move the task from Blocked to In Progress, not back to the Backlog.

Steps to reproduce

1. Execute a task and let it become blocked while its executor poller remains alive, such as at a permission prompt.
2. Press Shift-S and change its status to In Progress.
3. Observe the task briefly enter In Progress, then move to Backlog.

Expected behavior

The task remains queued/In Progress and resumes through a fresh executor run.

Actual behavior

The previous executor poller sees the internal queued status and returns Interrupted. Finalization treats that as a user cancellation and changes the task to backlog.

Relevant flow:

• showChangeStatus maps In Progress to StatusQueued.
• pollTmuxSession returns Interrupted: true upon seeing StatusQueued.
• executeTask handles every interrupted result by writing StatusBacklog.

This appears timing-dependent because it requires the previous poller to remain registered.

Suggested fix

Distinguish requeueing from genuine interruption. Preserve queued when the old poller exits, release its running-task slot, and wake the worker for a fresh execution.

Environment

• TaskYou: 0.3.18
• Go: 1.24.4
• OS: macOS 26.5.1, arm64

[kylecarbonneau]

This is more or less me looking for the temporary workaround to the current behavior that (most) of my sessions don't automatically go back into "in progress" once I have unblocked the session. So I tried manually updating the task status to clear my blocked queue. I'll submit about that issue separately though.

[bborn]

Fixed by #676 (merged to main — commit ccea2e0a).

Root cause: a blocked task's executor goroutine stays parked in pollTmuxSession. Moving it to "In Progress" writes status queued; the parked poller saw queued, returned an interrupt, and executeTask finalized every interrupt to backlog — undoing the requeue. Because a blocked task's poller is essentially always parked, this was close to deterministic, not a rare race.

Fix: distinguish a re-queue from a cancellation. pollTmuxSession now returns {Requeued: true} for the queued case, and the finalizer preserves queued (kills the stale session, wakes the worker) instead of writing backlog. The task resumes via a fresh run, as expected.

QA — reproduced end-to-end against an isolated instance, then verified the fix:

Blocked (before)	Bounced to Backlog (pre-fix bug)	In Progress (fixed)

Pre-fix: Blocked → In Progress → Backlog at t+1.1s. Fixed: Blocked → In Progress → stays In Progress / running.

Ships in the next release. Thanks for the precise report — the exact code path you named was correct.