Files
orca/config/scripts
Brennan Benson ac36377cac fix(terminal): guard SSH work on window close
The window-close guard selected local worktrees before probing, so every
direct-SSH pane was dropped unprobed and the window closed with no warning
over work still running on the remote host. A direct-SSH shell does not
survive the window, so "it runs elsewhere" was never a reason not to ask.

Drop the owning-host filter entirely rather than adding a parallel remote
branch: `inspectProcess` dispatches on the PTY id, so each pane is answered
by whichever host runs it (ssh-pty-provider's `pty.inspectProcess` request),
and the existing evidence read already carries the whole verdict vocabulary.
That also stops discarding a worktree whose repo has not hydrated yet, which
the `!== null` test read as remote.

Verdicts are unchanged and stay in window-close-running-process-evidence.ts:
`exited` is the only one that closes with no prompt. A relay too old to
answer `pty.inspectProcess` rejects with method-not-found and a dropped
connection rejects too — both are `unverifiable` and both ask. No missing
reply is ever spent as an observed absence. Runtime-environment panes stay
excluded: that host outlives this window by design.

The warning now speaks for remote panes too, so it no longer scopes itself
to local terminals; all five catalogs and the ja exact-match repair follow
the new English string. No new wire field and no new stream opcode.
2026-08-28 17:00:45 -07:00
..
2026-05-15 05:44:25 -04:00