fix(launch): stop the --print helper from clearing the pane badge

[NagyVikt]

What

announceTmuxProfile() gated only on process.env.TMUX, so every cue launch reached it — including the short-lived --print skill-selector cue spawns on each session start. That helper inherits TMUX_PANE from the session it is helping, so it wrote @cue_* onto that pane and then, seconds later, its process.on("exit") handler unset all eight.

The interactive session kept running with its badge wiped off the pane border: the profile name and icon simply vanished mid-session.

Evidence

Measured on a live machine: 1 of 12 panes still had @cue_profile_name set.

%22  cmd=bun  prof=coolify  icons=🧊
%9   cmd=bun  prof=         icons=
%12  cmd=bun  prof=         icons=
%21  cmd=bun  prof=         icons=
...

The helper is the one cue spawns itself — observed live as
bun cue/src/index.ts launch claude --print --strict-mcp-config --model haiku -p "You are choosing which skills to load…",
matching classifierSpawnArgs() exactly.

Fix — two guards, for two different cases

ownsPaneBadge() adds a TTY requirement. Verified against live processes: all seven interactive launchers write to /dev/pts/N, while claude-classifier.ts spawns with stdio: ["ignore", "pipe", "ignore"]. A pipe is precisely what separates a helper run from the session the user is looking at.

The exit sweep now checks ownership. It reads the eight options back and unsets only those still holding the values it wrote. This is not redundant with the TTY guard: a nested launch — supported since #119 — has a TTY too, so the guard alone would not stop it from clearing an outer session's badge when it exits.

The read-back is one extra spawn, batched through display-message -p with a \x1f separator, in keeping with the existing set/unset batching. A failed read-back leaves the options in place — leaking a stale badge is recoverable on the next launch, clearing a live one is not.

Tests

ownsPaneBadge is extracted as a pure predicate so the rule is explicit and covered: interactive-in-tmux owns it; piped does not; outside tmux nobody does; CUE_TMUX_TITLE=0 still opts out.

Verification

Check	Result
tsc --noEmit	Pass (exit 0)
biome lint	Pass — both files clean
New tests	4/4 pass
Full suite	28 failures, identical by name to main — zero new failures

The suite is red at baseline on main; the failing set was captured on both sides and diffed after stripping bun's per-test timing annotations.

🤖 Generated with Claude Code