Files
Neil 9bd6272fdf refactor(tooling): organize build, CI, and test owners (#38130)
* refactor(tooling): organize test runtime and maintenance owners

* test(tooling): preserve relocated runtime fixture dependency edges

* refactor(tooling): preserve xterm routing owner checks

* ci(tooling): include routing owner in sparse checkout

* test(tooling): preserve copied workflow dependency closures

* fix(tooling): normalize hashed JSON assets in release parity

* fix(tooling): distinguish asset aliases from literal references

* fix(tooling): frame normalized asset reference payloads

* fix(tooling): normalize decoded JSON asset references

* refactor(tooling): organize build, CI and release owners

* fix(tooling): align moved generator and workflow path contracts

* fix(tooling): update generated plugin bundle owner banners

* test(tooling): create relocated mobile verifier fixture directories

* test(tooling): copy headless detector dependency closure

* test(tooling): align native batch policy fixtures with owner path

* fix(tooling): link moved reliability command to historical evidence

* fix(tooling): preserve nested sandbox owners and canonical guide source

* fix(tooling): target release version owners in checkout fixture
2026-11-04 21:08:19 -08:00
..

Packaged Windows PTY native capability smoke

This narrow harness runs the packaged Orca.exe with ELECTRON_RUN_AS_NODE=1 and loads its bundled node-pty. Checkout Node processes provide the target/canary shell fixtures, so the smoke proves the packaged native addon without putting a GUI-subsystem Electron executable under ConPTY. A 256-bit fixture token binds the target shell, a grandchild that remains live after its intermediate launcher exits, and an unrelated canary to one unique named-pipe channel; the oracle checks the patched exports, job PIDs, exact job-handle termination, PTY/socket exit events, and canary survival.

Run it against an unpacked Windows package:

pnpm run smoke:windows-pty-native-capability -- --exe=dist/win-unpacked/Orca.exe

The official v1.4.158 package is the causal red artifact: it fails immediately because its packaged node-pty lacks assignCurrentProcessToJob. Candidate green evidence comes from the required Windows packaging job, which runs this smoke without retries. The one-shot probe flushes its evidence and exits explicitly because direct native job termination intentionally bypasses node-pty's ConPTY-worker disposal path; a 45-second outer ceiling reports bounded stdout, stderr, and native-stage breadcrumbs if any boundary stops progressing.