What happened?

After PR #297 changed the Todo dock to stay mounted "whenever the current session still has todo data", manually clicking the Stop button mid-turn makes the todo dock disappear instead of staying visible. The fix from #297 covers the natural-end-of-turn case but not the user-initiated stop path.

Steps to reproduce

1. Open PawWork (dev branch, post-fix: keep todo dock collapsed while todos exist #297)
2. Start a session and ask the model to do anything that uses the todowrite tool (e.g. "Plan a 5-step refactor and create a TODO list")
3. While the turn is still running and the todo dock is visible (with at least one item), click the Stop button on the composer
4. Observe: the todo dock disappears immediately

What did you expect to happen?

The todo dock should stay mounted and show the existing todos in its collapsed form, the same way it does when a turn completes naturally. The contract from #297 ("todos exist → dock visible") should also hold for user-initiated stops.

PawWork version

dev branch (post-#297, around 2026.4.29 release)

OS version

macOS 15.x

Can you reproduce it again?

Yes, every time

Screenshots, recordings, or extra context

Likely root cause: the stop handler resets some piece of session state that the dock-mount predicate reads to decide whether todos still exist, before the data is actually cleared. Worth tracing session-composer-state and the stop button's onAbort path; #297's mounting predicate probably needs to also tolerate the stopped state.