Shells keep running after their terminal tabs are gone, and ace kill leaves the tab on Connecting #622

Terminal shells keep running after their tabs are gone, with no way to find them, and ace kill leaves the visible terminal on "Connecting...".

What was seen

• Three shells from terminal tabs that weren't restored kept running in the lane: "Nothing in the app showed them, and nothing let me get back to them." Only ace kill ended them (^774, ^776). Tabs are kept per browser (^768), so anyone who opens the channel in another browser or device has the same blind spot.
• ace kill hello-notes printed nothing. The open terminal then sat on "Connecting..." with Agent access and desktop tools greyed out, through a wait and a reload. Only leaving the tab and coming back showed "The host no longer had this terminal's shell, so this is a new one…" (^776).
• Archive channel killed a running sleep 900 ("zsh: hangup sleep 900") without asking (^776).
• Cmd+A, Cmd+C, then Cmd+V pasted the whole screen and ran every line as a command with no multi-line paste warning: "zsh: command not found: ❯", "zsh: command not found: copy-me-757" (^757).
• ⌘K in a focused terminal cleared the screen instead of opening the palette (^765).

Steps

1. Open two Terminal tabs in a channel; open the channel in a fresh browser profile. The tabs aren't there; ps shows the shells.
2. ace kill <channel> while a terminal tab is visible.

Expected: the channel lists its running shells and lets you reopen or end them, ace kill says what it stopped and the tab recovers on its own, and Archive warns when terminals are running.

Rig: web (loopback source host from origin/main, 0.0.53 code).

Map: ^768, ^774, ^776, ^757, ^765.

Found in the 2026-10-22 map study.