Extract subprocess execution and process contracts into @orca/process-host with explicit public entry points, independent checks, and one Node 18 compatible CommonJS runtime. Migrate application consumers and integrate package builds, dependency selection, import enforcement, and runtime resource staging.
Preserve daemon startup ownership and profile isolation, and qualify development rebuild recovery and concurrent output publication. Remove unnecessary aliases, test forwarding exports, and a duplicate output scan.
Validation: full typechecks, changed-code quality, package and artifact checks, native Windows builds/types plus 306 runtime tests, and independent native reviews.
Matched full E2E controls on original main and unchanged reviewed head both pass all 17 applicable tests (nine skips). Earlier intermittent E2E failures are documented in the PR; no assertions were weakened. The final combined-tree audit preserves both branches with no import-boundary violations.
* test: reproduce accumulated-workspace typing latency through real PTYs
* test: make the bench harness self-checks falsifiable
Review found four assertions that could not fail and one fixture gap:
- `missingPtyArrivalCount`/`missingEchoCount` were hardcoded `0` and
`validateExpectedSeqs` throws before them, so every assertion on them
was vacuous and every report read `0`. The throw is the real guard and
is already covered; drop the vestigial fields.
- An absent status controller returned an all-zero result, which satisfied
its own accepted-equals-generated equality. Assert presence first.
- The byte-pacing control had only an upper bound, so a generator emitting
no stream bytes passed. Add the lower bound.
- `lineageEvery: 1` built zero lineage: no ordinal satisfies
`% 1 === 1`. Offset the interval and cover the densest setting.
- The documented control command never set ORCA_TYPING_BENCH, so it
skipped instead of running.
Neil
Jinwoo Hong