Files
orca/mobile/tsconfig.test.json
T
Brennan Benson f0d55e7319 Nest chat-UI orchestration workers under the agent that started them (#34601)
* Nest chat-UI orchestration workers under the agent that started them

Main's lineage projection only walked terminal panes, so workers running
in the chat UI never got a parent link and listed flat in the sidebar.
It now also projects chat workers, keyed by their visible chat row, and
resolves a chat creator or coordinator to that chat's visible row
instead of its handle or private mailbox pane key.

* Fix public worker lineage across assignment and row identities

* Complete terminal lineage provenance and bound active session selection

* Repair lineage test runtime boundaries and SQLite counters

* Batch public lineage verification after exact recency selection

* Use checked runtime values in lineage integration tests

* Document the trusted Dispatch SQL row boundary

* Keep lineage integration imports within their test programs

* Load native lineage fixtures before test execution

* test: complete lineage inputs in runtime and sidebar fixtures

* test: seed benchmark facts from active dispatches

* test: replace partial orchestration DB casts with typed fixtures

* test: complete stale-leaf mailbox fixture session input

* fix(test): render worker lineage fixture with production list
2026-10-28 16:06:38 -07:00

22 lines
1.2 KiB
JSON

{
// The main config excludes test files so Metro never compiles them into the release bundle, and
// vitest transpiles without typechecking — so until this config existed nothing typechecked a
// mobile test, and a type-level pin written in one proved nothing.
"extends": "./tsconfig.json",
"exclude": [
"node_modules",
// These tests are Node-side, not React Native: they import the desktop main process or
// @orca/process-host, whose modules are written against @types/node. This program's libs
// are React Native's, where `setTimeout` answers a number rather than a NodeJS.Timeout, so
// pulling that graph in reports ~280 errors about the desktop rather than about mobile. Their
// own runtime coverage is vitest, which runs them under Node.
"src/components/WorktreeAgentList.runtime-lineage.test.tsx",
"src/session/mobile-native-command-discovery.test.tsx",
"src/tasks/agent-launch-mobile-replay.test.ts",
"src/test-support/rpc-recording/recorded-request-params.test.ts",
"src/tasks/mobile-agent-launch-architecture.test.ts",
"src/transport/mobile-relay-browser-cancel-budget.test.ts",
"src/transport/mobile-web-bundle-host-slow-link.test.ts"
]
}