Files
orca/config
Jinwoo-H e9b5ae26b1 test(serve): pin zero duplicate agent resumes across headless serve desktop promotion
STA-1716 / #8457 acceptance criterion 6 asked for an automated regression over
desktop exit + surviving daemon sessions + headless serve lock owner + a GUI
activation attempt. The lifecycle fixes landed (#8646, #12212, #12574) but
nothing asserted the outcome the incident was actually about: how many agents
the promoted renderer resumes.

The new test drives the real modules end to end — packaged serve takes the
single-instance lock, a forced relaunch reaches its second-instance handler,
the activation gate coalesces until the persistent provider settles, one window
opens, and the renderer hydrating inside that process resumes zero agents both
before and after its panes rebind the surviving daemon PTYs.

settleServeDesktopActivation moves out of index.ts so the test exercises the
production decision instead of mirroring it.

Red evidence: reverting the hidden-pane ownership predicate to its pre-#12574
form launches 2 duplicate `codex resume` tabs; also zeroing the live-PTY check
makes both hydration passes red; dropping the duplicate-serve argv guard opens
a window for `--serve`; always marking the gate ready removes the fail-closed
diagnostic; refusing to open a window drops both promotion assertions.
2026-08-05 03:26:40 -04:00
..