Observed after recovering a Vite server in an existing sidemux-managed pane.
Reproduction:
- Start a background job and interrupt it.
- Rerun the saved command manually in the same pane through
send_keys.
- Wait until the new Vite process reports ready and begins listening.
- Call
list_panes, read, and wait for the pane or previous job.
Observed:
- The manually started server was healthy and listening.
- Sidemux continued to expose the previous job's
failed state.
read and wait returned stale output from the previous failed run.wait could time out despite the new process already reporting ready.
Expected:
A command started manually in a managed pane should either create a new tracked execution context or make the pane explicitly report that its foreground process is untracked. A previous job's exit status and output cursor should not be applied to the new process.
Related but distinct: #27 covered stale pattern matches within one tracked job, and #28 covered a tracked foreground job remaining active after the prompt returned. This case starts a new command in the same pane after the old job ended.
Observed after recovering a Vite server in an existing sidemux-managed pane.
Reproduction:
send_keys.list_panes,read, andwaitfor the pane or previous job.Observed:
failedstate.readandwaitreturned stale output from the previous failed run.waitcould time out despite the new process already reporting ready.Expected:
A command started manually in a managed pane should either create a new tracked execution context or make the pane explicitly report that its foreground process is untracked. A previous job's exit status and output cursor should not be applied to the new process.
Related but distinct: #27 covered stale pattern matches within one tracked job, and #28 covered a tracked foreground job remaining active after the prompt returned. This case starts a new command in the same pane after the old job ended.