futpib / slopd

81%

master: 85%

Pull #23

github

fix: guard Run handler from resetting pane state that a concurrent hook already advanced

A race condition caused slopctl send to wait indefinitely (60 s) for
a pane to become ready after slopctl run returned.

After `tmux new-window` returns, mock_claude is already running in the
new pane. The Run handler then inserts the pane into managed_panes
(making it eligible for hooks) and awaits two tmux set-option calls
before finally calling set_pane_detailed_state(BootingUp). During
those async yield points a concurrent Hook handler task (processing a
`slopctl hook SessionStart` connection from mock_claude) can run and
set the state to Ready. When the Run handler resumes it then calls
set_pane_detailed_state(BootingUp) and resets the state, leaving
slopctl send waiting indefinitely for a Ready event that never comes.

Fix: read the current in-memory state under the mutex lock and skip
the set_pane_detailed_state(BootingUp) call if a hook has already
advanced the state beyond BootingUp. PaneState::new() already
initialises detailed_state to BootingUp, so the pane is correctly
initialised regardless.

Agent-Logs-Url: https://github.com/futpib/slopd/sessions/7e1728d8-83a2-4ae7-a812-a0db819855a4

Co-authored-by: futpib <4330357+futpib@users.noreply.github.com>

28 of 34 new or added lines in 2 files covered. (82.35%)

1629 of 2007 relevant lines covered (81.17%)

112.71 hits per line