Commit Graph
18342 Commits
Author SHA1 Message Date
Neil 13f390f4f5 fix(wsl): retry the setup-runner .git link read and fall back to the distro's Git (#36792)
* fix(wsl): retry the setup-runner .git link read and fall back to the distro's Git

A Windows stat over \\wsl.localhost can report a transient ENOENT. Retry the link read once,
then ask the distro's Git asynchronously (fenced) before failing setup-script creation.

* fix(wsl): map a mounted-drive Git answer to its Windows drive
2026-10-31 16:22:24 -07:00
NeilandClaude 9c29a922d6 fix(wsl): hide the D1c Settings rows whenever WSL hosts take no new work (#36808)
* fix(wsl): hide the D1c Settings rows whenever WSL hosts take no new work

The Windows-drive Git row and the drive-path conversion row showed with the
WSL hosts setting on and preload present, so in serve-only or after a live
policy block they stayed and failed on click with *_unavailable, since main
now gates both conversions on the opt-in. They now follow
useWslHostsAcceptNewWork, which also needs the setting, matching main.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(wsl): keep a converted project's Git state visible when D1c offers hide

WslDriveProjectGitRow is also the read-only row saying Orca runs Git on
Windows for a project with git: windows-host, a preference that still
applies with no new work accepted. The row now always renders that state
and hides only the Use Git for Windows offer, through a new acceptsNewWork
prop; the drive-path conversion row, offer-only, stays hidden as before.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-31 16:21:26 -07:00
Neil 7dbe93149d refactor: colocate structured session live reads and reconnect scheduling (#36807) 2026-10-31 16:20:18 -07:00
Neil 964fe5b73c fix(wsl): a restored chat or a web hooks check never starts a stopped distro (E9) (#36779)
* fix(wsl): a restored chat or a web hooks check never starts a stopped distro (E9)

A chat pane mounting on launch restore or a remount read its transcript as a
user open and booted the transcript's stopped WSL distro. Only the mount that
the user's own switch caused, and paging, now ask main to start it; otherwise
the read refuses and the pane shows the distro's stopped copy at once (a
stopped UNC transcript was reported as missing and spun as pending).

A web client sent repo.hooksCheck without background, which a server treated
as a launch that may open the distro. The server now opens it only for an
explicit wakeWslDistro; clients send it for launches and keep background for
older servers.

* fix(native-chat): key a chat's open wake on its own workspace; update wake assertions

A chat in another workspace mounting inside the switch window no longer takes the
switch's wake. The paging and worktree-removal assertions now expect the explicit
wakeWslDistro flag.

* fix(native-chat): set the pane-key ref in the layout effect, not during render
2026-10-31 16:17:55 -07:00
Neil 7ee9816b84 fix(markdown): keep the Mermaid expand button out of PDF and HTML exports (#36631) 2026-10-31 16:07:52 -07:00
OrcaWinandOrcaWin de2dac447a test: remove 512 low-value tests (#36794)
* test: remove low-value suites and cases

* test: remove orphaned preamble snapshots

---------

Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
2026-10-31 23:01:58 +00:00
Neil 1526c7e041 refactor: group agent-session background-task modules (#36798) 2026-10-31 15:52:18 -07:00
NeilandClaude f2731a2cfc feat(wsl): a WSL hosts block learned mid-run stops new work at once (#36776)
* feat(wsl): a WSL hosts block learned mid-run stops new work at once

The live policy fetch caches a newly published block, but the gate is
fixed for the run, so the add-host and move entry points and the
in-context offer stayed until the next launch. A block the fetch learns
now stops new work in-session through one predicate,
wslHostsAcceptNewWork(): adding hosts, starting or previewing moves,
automatic and opened-project moves, and Retry. Main pushes the capability
to the renderer, which hides the offer and entry points. The gate and
what is served are unchanged until the next launch, so saved hosts and
moved projects keep working, and cancel, Restore and Not now stay.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(wsl): a live block also ends Stage 1 opt-in and stops mid-step host adds

Review follow-ups:
- wslHostsOptedIn now also needs wslHostsAcceptNewWork, and the Git router
  re-applies its opt-in when a block lands, so the D1c router and the
  background WSL Git gate uninstall at once, as turning the setting off does.
- D1c conversions (wslDriveProject preview/convert, wslDriveUnc:convert)
  gate on the opt-in; the new-project Git default already did.
- The orchestrator re-checks before adding a host, so a step already past
  its start gate adds nothing after a block.
- The window broadcast and capability push move to
  wsl-host-window-broadcast.ts, keeping wsl-host-handlers.ts under max-lines.

Co-Authored-By: Claude <noreply@anthropic.com>

* test(wsl): keep gate mocks whole, and pin cancel after a live block

The visible-work lifetime suite mocked the gate with one export, so the
handlers' new wslHostsAcceptNewWork and onWslHostsNewWorkChanged calls
failed it; it now spreads the real module and overrides only what it
needs. A new case pins that cancelling a running move still works after
a live block while a new move is refused.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-31 15:45:48 -07:00
Neil 4d4da6f49f fix(wsl): offer Start wherever a stopped WSL host leaves the workspace stuck (#36786)
* fix(wsl): offer Start wherever a stopped WSL host leaves the workspace stuck

The stopped card with Start only appeared inside a terminal pane. A file-only
or empty workspace on a stopped distro showed a read error or nothing, with no
way to start it. The editor, Explorer and Source Control error states, the
empty workspace, and the host and workspace row menus now show
"<distro> is stopped" with Start. Only the click boots the distro (E9).

* test(sidebar): stub the stopped-host Start item in context menu tests that mock a partial store
2026-10-31 15:33:52 -07:00
Neil 7a25d8592f refactor: import Codex session types from defining owner (#36785) 2026-10-31 15:26:22 -07:00
Jinwoo Hong e4dedf2a7e Keep orchestration inbox output short (#36626) 2026-10-31 18:23:01 -04:00
Jinwoo Hong c408634ada Orchestration: keep open workers started in a new workspace (#36782) 2026-10-31 18:07:30 -04:00
Neil 0483d02e60 fix(wsl): keep WSL exec checks off the main thread and share running-list reads (#36777)
- Codex managed-home ownership check runs async in the distro via runWslProcess, fenced
- transcript running observer reuses fresh running-list reads; 5s cadence, first look at 2s
- synchronous Git refuses a WSL cwd; the setup runner reads a WSL worktree's .git link instead
2026-10-31 14:55:56 -07:00
OrcaWin a489b24748 test: remove 246 low-value tests (#36780) 2026-10-31 21:52:07 +00:00
Jinjing c6e6387889 feat: make the workspace name emoji picker discoverable (#36761)
* feat(sidebar): add emoji picker button to workspace display name field

The Display Name field supported :shortcode autocomplete, but nothing on
screen said so. Add a smiley button inside the field that opens the
existing lazy-loaded emoji picker and inserts at the caret. Its tooltip
mentions the : shortcut.

* fix(ui): use Input adornment variant instead of ad-hoc padding classes

* feat(new-workspace): add emoji picker button to Create worktree name field

Show the button in Smart and Name modes (not search-only tabs). The
picker portals into the enclosing dialog so its search box can take
focus inside the modal focus trap, and opening it closes the source
results list.

* feat(workspace-emoji): replace emoji-picker-react with a compact native picker

The stock library picker looked out of place in Orca's dialogs (oversized
search, skin-tone swatch, large category bar). Build a small panel on the
shortcode catalog the : autocomplete already loads: compact search, a
curated 8x6 grid of workspace-friendly emoji, search results while typing,
arrow-key navigation, and a footer showing the :shortcode: to teach the
shortcut. Drops the 500KB library chunk from this feature.

* fix(workspace-emoji): match the : suggestion list and stop clipping in dialogs

Restyle the picker as a searchable version of the : shortcode list using
Command's supported variants. Portal it to the body instead of the dialog
element, which clipped it at the dialog edge; Radix pauses the dialog's
focus trap for nested layers, so the search box still takes focus.

* perf(workspace-emoji): lazy-load the picker panel and keep typing re-render free

- Lazy-load the panel with lazyWithPreload, preloading on hover/focus
- Memoize the button and read the input value at pick time, so it no
  longer re-renders on every keystroke
- Store the curated defaults as literal pairs so opening the picker never
  builds the full shortcode catalog (was ~9ms on first open)
- Stop Enter/arrow keys in the picker from reaching the source Command

* perf(workspace-emoji): keep picker defaults out of boot and skip keystroke re-renders

- Move the curated defaults into their own module so only the lazy panel
  chunk ships them
- Pass a stable (useLatestHandler) value handler from the Smart field so
  the memoized button does not re-render per keystroke
- Add a render-count test that fails without memo

* fix(workspace-emoji): re-render the memoized picker button on UI language change
2026-10-31 14:44:14 -07:00
Neil ca07c135f9 fix(wsl): Stage 1 is opt-in: the offer moves only its project, and D1c Git follows the setting (#36773)
* fix(wsl): Stage 1 is opt-in: the offer moves only its project, and D1c Git follows the setting

* fix(wsl): the WSL path access-denied explanation follows the setting too
2026-10-31 14:39:27 -07:00
NeilandClaude 19a73ff0b4 fix(wsl-host): keep a host's launch markers out of its shells; a corrupt WSL store hides only WSL hosts (#36772)
- ORCA_WSL_ORCAD_HOST and ORCA_WSL_DISTRO_GUID joined the server launch env both pane spawn
  paths scrub (one shared list with the activation root and idle window), so a user's own orcad
  started in a host shell no longer acts as a WSL host.
- An unreadable orca-wsl-host-deployments.json (corrupt, or a newer envelope) used to fail the
  whole server list closed while hosts were served, hiding every SSH and paired server. It now
  hides only the servers that could be WSL hosts, logs why, and writes still refuse the file so
  a newer build's copy is kept.

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-31 14:39:16 -07:00
Neil c698112b83 fix(windows): stop WSL host servers before releasing holders, in a fixed budget (#36769)
* fix(windows): stop WSL host servers before releasing holders, in a fixed budget

Uninstall released the holders first, so the server stop could exec into a
distro already idling out. Servers now stop while the holders still keep
their distros up, then the holders go. The stop also no longer spends one
wsl.exe and cold guest CLI per terminal: it closes every worktree's
terminals in parallel in one call and waits for the census inside the
guest in one more, so 20 terminals cost the same four calls as one. The
per-distro budget is 30 s and the preflight cap 60 s.

* fix(windows): end an uninstall server stop's wsl.exe calls when its budget runs out

decommission ran its own wsl.exe calls outside the abort signal, so after
the per-distro timeout they could outlive the holder release and boot a
distro that had idled out. The WSL transport now takes the budget's signal:
once aborted it starts no wsl.exe and ends running ones, and the stop waits
up to 2 s for them to unwind before the holders are released. The census
waits in the guest against an overall 8 s deadline, each call bounded at 4 s.

* test(windows): pin failed uninstall closes and the default census retries
2026-10-31 14:37:36 -07:00
Neil 76e5e94b23 refactor: colocate structured session tool-call projection (#36770) 2026-10-31 14:25:20 -07:00
OrcaWin 7467a4afc1 docs: clarify low-value test removal guidance (#36768)
* docs: clarify low-value test removal guidance

* docs: remove test removal preamble
2026-10-31 14:10:06 -07:00
OrcaWin 0d9e02754e test: remove low-value suites and cases (#36766) 2026-10-31 14:10:00 -07:00
Jinwoo Hong 182190269c Tell coordinators to keep open workers the user will keep using (#36764) 2026-10-31 17:08:09 -04:00
Neil f0a1ae3fe6 refactor(shared): colocate compaction and command entry owners (#36738) 2026-10-31 14:00:35 -07:00
Jinjing 21c86904d5 fix(menu): use native DevTools routing outside managed pages (#36763) 2026-10-31 13:40:26 -07:00
Neil 6e40e3721b fix(wsl): restoring or switching to a WSL host workspace never boots its stopped distro (#36688)
* fix(wsl): restoring or switching to a WSL host workspace never boots its stopped distro

A launch booted the last focused WSL host's distro from an early-wake list,
and the window's focus report (sent for a launch restore as well as a click)
connected the host with boot allowed. Both started a distro the user had
stopped, and the stopped card never appeared. Focus now re-checks and
connects only a running distro; a stopped one is published stopped, so the
panes show Start. Start and New Terminal still boot it. The early wake is
gone, and a launch deletes the list an older build left.

* fix(wsl-host): a stale stopped read never overwrites a newer connect

A focus re-check that read the running list while the distro was stopped
could finish after a user Start or New Terminal had connected, then publish
distro-stopped with terminals exited over the live host. Every ready publish
now bumps a per-host generation; a runtime call whose read a newer ready
overtook re-checks instead of parking.
2026-10-31 13:37:20 -07:00
OrcaWin 47a2a953c6 test: remove 206 low-value tests (#36759) 2026-10-31 20:34:03 +00:00
Neil ee44140fb9 fix(terminal): scope terminal color overrides to their light/dark theme slot (#36581) 2026-10-31 13:12:56 -07:00
Jinjing 119aafe0ca fix(ui): widen quick commands dropdown (#36757)
* fix(ui): widen quick commands dropdown

* fix(ui): retain dropdown primitive spacing
2026-10-31 12:58:48 -07:00
Jinjing e8a0e4e26b Use midpoint gray for default dark theme text (#36756) 2026-10-31 12:39:05 -07:00
OrcaWin 19d6957127 test: remove 272 low-value tests (#36750) 2026-10-31 19:36:52 +00:00
Jinjing 474e48a306 fix(shortcuts): avoid Plugins strikethrough shortcut conflict (#36741)
* Change Plugins shortcut defaults by platform

* Test Plugins shortcut matching on all platforms

* Test current Plugins default in browser shortcut forwarding
2026-10-31 12:27:32 -07:00
OrcaWin 10e35fd76d test: remove 226 low-value tests (#36737) 2026-10-31 18:55:29 +00:00
Brennan Benson cca9ed5a7a fix(github): make Checks refresh start a new PR read (#36651)
* fix(github): start explicit Checks refreshes after the action

* fix(github): give explicit Checks refreshes fresh checks and comments

The same Refresh or Link click that now reads PR metadata after the
action also reads checks and comments after it: an explicit request no
longer joins or waits on a read begun before the click, in the renderer
or (for checks) the host coalescer. A superseded read's callers show the
owner's answer, so a late pre-click reply cannot repaint the panel, and
comments posted during either read are kept.

A lost IPC/RPC reply is reported only to the click that asked; polls stay
silent as before, and a later answer clears a failure older than itself.
The manual hook takes its verdict from its own lookup, the link flow's
card-read failure no longer skips checks, and the web shim forwards the
intent.

* fix(github): land the older Checks reply when a newer explicit read fails

When a click's checks or comments read fails while the read it replaced
succeeds, the click's read now lands that older reply through its owner
path instead of leaving the cache behind it. Post-write comments
refreshes (mutation events, bulk resolve) carry the explicit intent so
they cannot be answered by a read begun before the write.

* test(github): drop type assertions from the explicit-refresh tests

The RPC tests call the handlers with a real runtime service and spies,
and the panel test passes typed fixtures straight to the hooks.

* test(github): type the Checks panel fixtures for the renderer project

The renderer tests build their PR fixture locally instead of importing a
main-process harness, and the panel setter mocks take the hooks'
SetStateAction form.
2026-10-31 11:10:38 -07:00
Neil df9ad9da84 refactor(shared): colocate session failure detail readers (#36727) 2026-10-31 11:05:39 -07:00
OrcaWin 3c5773c04d test: remove 187 low-value cases including six whole suites (#36724) 2026-10-31 18:05:10 +00:00
Neil 24d1d10da8 refactor(shared): colocate session thread-goal contracts (#36720) 2026-10-31 10:30:42 -07:00
Brennan Benson c64e1f615a Preserve queued command and card order through recovery (#36430)
* Advertise mid-turn queueing as queued-messages.v2

Released clients read the v1 name with an unfinished queue UI; they never
see v2 and keep sending immediately.

* Let each desktop send choose queue or steer while the agent works

The follow-up choice is now a Queue / Steer setting saved under
nativeChatFollowUpBehavior, Steer by default; the old
nativeChatQueueFollowUps switch, which every install saved as true
while queueing was dark, is retired on load. Every reader goes through
native-chat-follow-up-behavior.

While the agent works, Enter follows the setting and Cmd/Ctrl+Enter
sends the draft the other way; the alternate flips the setting before
the queue's own rules (a waiting command still queues, prompts no one
here can answer still send now) and never applies while Stopping.
Cmd/Ctrl+Shift+Enter steers the head card only and leaves the draft.
An idle agent's card reads Send, and the card menu no longer offers
"Turn off queueing".

* Hold Send on the phone to queue or steer a message mid-turn

While the agent works on a host that queues, holding Send opens a
Queue / Steer sheet; a choice other than the host's setting sends the
alternate, resolved against the chat as it is when it lands, by the
desktop's rule. Release and dismiss send nothing. The phone reads the
host's new follow-up setting (absent reads as Steer), and an idle
agent's card reads Send.

* Read the follow-up default from one place on desktop and phone

* Keep phone follow-up choices aligned with live host state

* Update stream and wire fixtures for live follow-up preferences

* Document minimal runtime test fixture assertions

* Keep mobile preference tests in the mobile compiler project

* Preserve queued input order through handover and recovery

* Consolidate input selection type imports

* Keep queue request capability types in the shared compiler graph

* Preserve reopen admission context and bound queue projection work

* feat(native-chat): queue follow-ups by default with a toggle

* fix(tests): preserve projection contracts in the node compiler

* fix(native-chat): retain receipt lookup after journal replacement

* test(mobile): assert shared preference renders on real changes

* Remove obsolete follow-up option translations

* Preserve input places across journal recovery without predecessor snapshots

* Keep recovered card placement tied to the exact handoff

* Preserve replay source types and correct verification fixtures

* Complete indexed queue selection and recovery ordering

* Preserve queued input order across recovery and source replay

* Fix legacy queue recovery fixture types

* Use a specific name for queue pause inputs

* Preserve fallback queue identity across journal recovery

* Place nested storage negative directive on its constrained call

* Constrain journal draft property type parameter

* Remove journal input order import cycle

* Preserve lazy journal counter reads within line limit

* test: preserve legacy conversion and display work contracts

* test: align journal refusal and restore accounting contracts
2026-10-31 10:17:56 -07:00
Brennan Benson de192f1e96 Native chat: Stop turns into Send while you type a follow-up, with a shortcut hint (#36655)
* Turn Stop into Send while the agent works and a draft has text

While the agent works, the desktop composer's Stop button becomes the
ordinary Send button once the draft holds text or images, and returns to
Stop when the draft is empty. It sends like Enter, so it follows the queue
setting; Esc still stops. Its tooltip names what Cmd/Ctrl+Enter does
instead (steer when queueing is on, queue when it is off), read from the
same resolver the send uses, so it is absent wherever the shortcut would
send no differently.

The Send/Stop decision moves into native-chat-composer-send-state so the
pane stays within its size limit.

* Tie alternate delivery hints to the composer submission

* Combine duplicate composer test imports

* Return snapshot results from composer option fixture
2026-10-31 10:17:31 -07:00
Brennan Benson a2235ad4b9 fix(native-chat): new chats' model picker opens with the full list instead of a partial one (#36646)
* fix(native-chat): show the account's model list while a new folder's own listing runs

A new Claude or Codex chat in a folder with no saved model list showed only its remembered model (or nothing) until that folder's model probe finished, then the full list appeared 1-2 s later. Every new worktree and every chat after a restart hit this, because these agents keep one list per folder and the account-level list reads already fall back to was never written.

The account's own listing (prewarm names no folder) now also saves that list, and a read whose folder isn't listed yet answers from it, including before its scope resolves. The stand-in names no default as the folder's; the folder's own listing still replaces it.

* fix(native-chat): preserve account catalog publication ownership

* fix(native-chat): retain scoped account inventory under binding pressure

* test: make passive catalog deadline coverage deterministic

* test: consolidate catalog fixture type imports

* test: repair catalog fixture types and integration placement

* fix: retain accepted model catalog authority during refresh
2026-10-31 10:10:30 -07:00
OrcaWin 7556133a5a test: remove 266 low-value cases including 11 whole suites (#36717)
* test: remove low-value suites and cases

* test: update wall-clock baseline after case removal
2026-10-31 17:10:11 +00:00
Brennan Benson 07813de4b3 Let workers follow up with their own finished helpers (#36663)
* Allow workers to continue their own finished helpers

* Own helpers follow takeovers and who holds the agent; refusals after closing a leftover shell say so

- A worker's own-helper check now walks back from the caller through follow-ups and through exact pane takeovers recorded in the terminal's ordered owner history, same Run at every hop, so the documented reopen-on-the-same-agent recovery keeps the worker's helpers while a stop in another Run does not.
- The helper's owner is the creator of the Dispatch that last took custody of its agent, so a coordinator attempt that never got an agent no longer takes the helper away; a real coordinator takeover still does. With no custody at all the follow-up is refused.
- The refusal names the Dispatch the sender addressed (and its latest work when that differs) and says what to do instead.
- Follow-ups check nesting depth before placement can close a leftover shell; if a later check refuses after that close was requested, the error keeps its code and cause but says the close was requested instead of claiming no effects.

* Cover takeover ancestry, custody ownership and post-release refusals in the helper follow-up CLI test

Recovery-flow takeover (live, closed, unreadable history), takeover plus fresh follow-up composition, a stop in another Run, failed coordinator attempts, a real coordinator takeover, depth before and after release, refusals after a leftover-shell close, held-mail follow-through from own and foreign senders, and the ancestry read bound now counting custody-history reads. Error data is asserted, not only text.

* A helper that never got an agent stays its requester's

When no Dispatch in a helper's lineage ever took custody of an agent, its owner is the creator of the first Dispatch in its follow-up chain (every link read, same Run, no cycles), checked through the same caller continuation as before. A worker can again continue its own helper whose start failed before an agent came up, including after coordinator attempts that also never got one; a real coordinator takeover still blocks it. The round-1 denial for this case is gone. The post-release refusal rewrite names the message convention it relies on.

Tests: terminal-create and native setup-gate failures, failed coordinator attempts before a continued worker's retry through both addresses, takeover then an unplaced attempt, coordinator/foreign/missing/cyclic/cross-Run origins, and held mail on a failed coordinator attempt. The CLI fixture moves to a shared test-support file and ownership cases to their own file, which keeps each under the line limits.

* A worker reopened on the user's own terminal keeps its helpers

The own-helper ancestry also follows an external pane's previous holder. Each check reads the pane's complete assignment history once, from dispatch_contexts through a new full-history index on pane leaf and host (created on every open, so existing databases get it too), reading the exact-host and unknown-host cohorts and joining each holder's own custody row. Custody rows are inserted at acquisition, so original-acquisition rowids order the holders; timestamps and acceptance order are never used. The immediate predecessor is fixed before any check: if any holder lacks its own orderable row (a direct dispatch to the same agent, a backfilled, transferred or unreadable row, an unknown host), no edge is derived. The predecessor must then be the same process, same host and settled, and the walk keeps same-Run-per-hop and its seen set. The derived order lives only for that check. External rows stay external and gain no cleanup.

Tests: live and closed recovery on the user's terminal with equal timestamps, composition with a follow-up in a new pane and a takeover, another Run's assignment accepted after but acquired before the recovery, a real direct dispatch in between, replaced process, other host, backfilled and unreadable rows, held mail, a restart with the index rebuilt on an existing database, and read/plan contracts for unrelated history, one long pane chain and two panes joined by a follow-up at N and 10N. Ownership and core test files consolidated.

* Find a worker's former custody through its process identity, once per check

The own-helper walk no longer scans every custody row's owner history for each ancestor. It reads the Dispatch's own row by owner first; for a former holder it reads the custody rows of that Dispatch's exact process and host through the identity index, keeps the one whose ordered owners name it, and takes the owner right before it. Each identity cohort, decoded owner history and pane order is read at most once per check and dropped when the check returns. The shared former-owner reader and target routing are unchanged.

Tests: the call-count contract is replaced by read contracts over the actual SQL: a four-recovery chain reads one identity range visiting one row whether 40 or 400 unrelated Dispatch and custody rows sit beside it, with indexed plans and no former-owner scan; a 3- and 30-step follow-up chain reads one identity range and decodes the same number of histories.

* A direct dispatch before a worker no longer cuts it off from its helpers

A direct dispatch claims the user's pane in the Dispatch row it inserts, with no worker row and no custody row, so its insertion order bounds where it can sit. The pane history now reads each holder's Dispatch insertion order and whether it has a worker row, treats only that claim shape as a direct claim, and keeps the latest claim's insertion as a floor: an earlier holder is reachable only when it was inserted after every direct claim on the pane. Insertion order is never compared with custody order. Every other holder whose place is unproven still blocks the whole pane, and the floor is computed once per pane per check.

Tests: live and closed recovery after a direct dispatch before the worker (also from another Run), the claim between a worker and its recovery blocking only that edge while the next recovery keeps the reopened worker's own helper, a supervised Dispatch without its own custody row still blocking, and the history read contracts extended with old claims and the worker-row probe.

* Tighten the helper follow-up CLI tests

Drop the coordinator row from the refuse-after-release cases, which takes the same follow-up path as the worker's, and give the three-caller zero-effects case the refusal each caller gets.

* Count the former-owner scan's visited rows in the caller read trace

* Continue a worker's helpers only through recorded custody, finding each former holder once per check

A worker re-placed on a terminal it never held in saved custody no longer
inherits helpers from an earlier start there: the pane-history derivation
and its index are gone. Former custody is found by exact process through
one membership map per identity, so the walk is linear in ancestors and
rows.

* Pin the narrowed custody walk: one refusal for the user's terminal, linear identity and probe contracts

The external recovery tests and their pane-history contracts go. One case
pins that a worker re-placed on the user's own terminal is refused its
earlier helper with no effects while the coordinator still continues it.
The follow-up chain contract now grows both ancestors and same-process
rows and bounds field reads and Dispatch probes; the never-placed matrix
bounds the walk to the first request.

* Use a fixed observation time in the reopened-helper test

The provider session's observation time is never read on this path, so
the wall clock added nothing but a flaky-test gate failure.

* Drive the helper follow-up CLI tests through the runtime's own RPC server

The CLI now reaches the test runtime as it reaches the app: through the
metadata the real RPC server publishes, its socket, dispatcher and error
mapping, instead of module mocks of the runtime client and printer.
Recorded SQL rows are parsed into a named row type before their reads
are counted.

* Type the helper follow-up test traces without assertions

The SQL trace spies on each statement method through its own typed
signature and reads plan rows as the rows they are; the Dispatch probe
trace spies on each read separately; the never-placed matrix picks its
requester and corruption by origin.

* Type the CLI output spy as a console.log mock instance

An instantiation expression over spyOn's overloads named its type, and
this vitest's typings reject it; MockInstance names the spy directly.
2026-10-31 10:06:41 -07:00
Neil 4365547899 refactor(shared): colocate legacy session child-work projection (#36711) 2026-10-31 09:48:29 -07:00
OrcaWin 8d475840bf test: remove 16 low-value suites and 138 individual cases (#36710) 2026-10-31 16:00:41 +00:00
Neil 893152fa0c refactor(shared): colocate structured session event coalescer (#36708) 2026-10-31 08:40:13 -07:00
OrcaWin fe4595d6d6 test: remove 11 low-value suites and 157 individual cases (#36703)
* test: remove low-value suites and cases

* test: preserve historical reliability gate evidence
2026-10-31 15:27:20 +00:00
Neil 2487a258fe refactor(mobile): colocate chat pair-window regression test (#36702) 2026-10-31 08:00:31 -07:00
OrcaWin a0f75207ce test: remove 17 low-value suites and 133 individual cases (#36700) 2026-10-31 14:38:33 +00:00
Neil 6071220177 refactor(mobile): colocate native chat readability hook and tests (#36699)
* refactor(mobile): colocate native chat readability hook and tests

* refactor(mobile): use concrete readability module type in recorder
2026-10-31 07:37:09 -07:00
OrcaWin 1da1099dad test: remove 14 low-value suites and 241 individual cases (#36693) 2026-10-31 14:07:33 +00:00
Neil 1804e44610 refactor(mobile): colocate chat pinch gesture hook and tests (#36690) 2026-10-31 06:43:57 -07:00