[GeoffChurch]

Issue Link

Discussion #440

AI Policy Ack

ack

Drafted with vibes, edited and tested with meat

This PR was:

• mostly or completely vibe coded
• mostly or completely meat coded
• bit of both

Description

Adds window_title to the output of shpool list --json:

{
  "sessions": [
    {
      "name": "djt-miner",
      "started_at_unix_ms": 1790885744638,
      "last_connected_at_unix_ms": 1791385820043,
      "last_disconnected_at_unix_ms": 1791383990390,
      "status": "Disconnected",
      "shell_pid": 51725,
      "attachments": [],
      "window_title": "Coins mined: 23.203 ($0.00032). Level: patriot"
    }
  ]
}

The use case is letting downstream tools show the user the window titles of their sessions. Many processes (shells, coding assistants, etc) send status information to the window title, which is traditionally visible in a terminal window/tab but in shpool is inaccessible without attaching to the session.

This change exposes the current title through shpool list --json without attaching.

[ethanpailes]

I think you'll need to pull in shpool-vterm 0.2.7 (shell-pool/shpool-vterm#12)

[ethanpailes]

I'd like to take a different approach to avoid double-storing the same data.

[ethanpailes]

I just bumped the shpool-vterm version to 0.2.8, so you should be able to rebase and impl

[ethanpailes]

Draining other incoming requests immediately seems overly complicated. Let's just handled one at a time and use the top level dispatch loops for all incoming requests.

[GeoffChurch]

Done.

Or, maybe we could at least continue; after shell.rs:541 (like maybe_switch does on shell.rs:523), which would let it handle bursts without the hacky inner loop. Burstiness is the typical case in my workflow since I have k running instances of the TUI app, and they all call shpool list --json at the same time to refresh their view whenever the events channel sends anything.