Merge upstream 62d98096ca0d into atli

[gabynevada]

Merges upstream commit 62d9809 (761 commits after #22). Merge with a merge commit.

This stops one commit short of upstream's tip, 1451e7cb23 (in-app browser search engine). That commit passed CI, but it has collected 1,587 check suites while it is upstream's tip, and GitHub's commit check-runs API only returns the newest 1,000. scripts/fork-check.ts therefore can't see its Check and refuses it. The next update picks it up.

Conflict resolutions:

• pnpm-workspace.yaml / patches/expo-widgets@58.0.20.patch: upstream moved to expo-widgets 58.0.20, which already imports io.github.expo.peek, so the fork's fix(mobile): expo-widgets 58.0.18 compiles on Android #25 import rename is dropped and upstream's patch is used unchanged. The shiki-engine fbjni patch stays (still React Native 0.88.0, shiki-engine 0.3.12). Upstream's @expo/ui 58.0.20 and @expo/fingerprint entries are kept.
• NativeSwitch.android.tsx: upstream fixed switches inside pressable rows its own way (fix(mobile): prevent environment row taps from swallowing switches pingdotgg/t3code#17677: the Pressable owns the touch). The file now matches upstream, and the fork's responder hunk is dropped.
• ScheduledTaskService.ts: upstream fix(server): thread-bound scheduled tasks run on the thread's current provider pingdotgg/t3code#18467 makes the same fix as the fork (bound runs follow the thread's current provider), so this is upstream's version. The fork's "Uses this thread's current provider and model" settings row and followsThreadModelSelection stay, in web and mobile.
• AdaptiveWorkspaceLayout.tsx, useThreadHeaderOptions.tsx, ThreadPullRequestsPanel.tsx, ScheduledTasksSettings.tsx, SettingsScheduledTasksRouteScreen.tsx, NewTaskDraftScreen.tsx: upstream moved these to the React Compiler (no manual useMemo/useCallback). Each takes upstream's version with the fork's additions re-applied in that style. The search button upstream removed from the duo header is gone.
• ThreadHeader.tsx: the fork's Android thread-actions menu keeps the git and merge-back actions, and uses upstream's new merge glyph.
• MCP schedule_task description, ACP and OpenCode adapters: both sides kept (upstream's untrusted-webhook sentence and slash-command check, plus the fork's PR-watch flag).
• selfUpdate.test.ts, runtimeLayer.test.ts, orchestrationV2PendingBackgroundWork.test.ts: both sides' tests kept.
• pnpm-lock.yaml: upstream's, regenerated with vp i. It differs from upstream only by the fork's three patches (effect, react-native-image-viewing, react-native-shiki-engine).

Fork code that needed changes for upstream (it merged cleanly but broke typecheck or tests):

• Mobile ThreadRouteScreen: upstream dropped its useMemo/useCallback imports, so the fork's thread-action handlers are plain functions now.
• Two new upstream PR-watch tests in runtimeLayer.test.ts provide ServerSettings, which the fork's watch setting requires.
• ProviderSwitch.integration.test.ts (separate commit): upstream fix(server,mobile): a message you send resumes a held queue, and mobile can resume one pingdotgg/t3code#21473 releases a held queue when the user sends a message from a client. The provider-switch scenarios change the selection while the queue is held, so that message now comes over MCP, which keeps the hold. Delivered runs are looked up by id because they move after the message that ran ahead.
• fork-ci.yml and fork-full-suite.yml (separate commit): upstream's web tests now run a headless Chromium project through Playwright 1.60.0, which neither fork workflow installed. Fork CI's first run on this PR failed only because that browser was missing. Both now install it the way upstream's CI does (playwright install --only-shell chromium); the full suite needs it too, or the next release's web shard would fail.

Verified locally: typecheck for mobile, web, server, desktop, client-runtime, contracts, shared, provider-acp and provider-opencode; lint and format on every hand-resolved file; node scripts/fork-check.ts passes (every fork test file in mobile, server, web, client-runtime, contracts, provider-core, shared and scripts). No upstream workflow was added, so none needs disabling.

Done by Claude Opus 5.5 in Claude Code (T3 Code).

🤖 Generated with Claude Code

[atli-skald]

Skald review status

Skald: findings need a response (failure) at review state version 30, head 063ecb3326f8dba96a66ec4210cde4924241fd86.

Blocking

• apps/mobile/src/components/ui/SegmentedControl.ios.tsx:43 — The new iOS implementation sends only option.label to UISegmentedControl and drops option.accessibilityLabel; the previous shared implementation applied that label to each accessible press target. — nobody has answered it
• apps/server/src/pullRequest/PullRequestService.ts:3267 — diffFiles.sliceKey omits the summary updatedAt discriminator used by diff(), so validation reuses the previous revision's file set while the displayed diff already uses the new revision. — nobody has answered it
• packages/client-runtime/src/pullRequestQuery.ts:70 — Inherited Object.prototype members pass the undefined guard and are assigned as filter values even though they are not supported enum values. The query token is also removed from the remaining text. — nobody has answered it

Cleared

Nothing is cleared at this epoch.

Blocking: 0. Advisory: 3. Cleared: 0. Fenced: 0.
Response required: 3.

Review rounds

• dc2605c80a3ffaaf692136c3340f44c5a4de30f0
• 063ecb3326f8dba96a66ec4210cde4924241fd86

[atli-skald]

Skald review findings

Reviewed head 063ecb3326f8dba96a66ec4210cde4924241fd86 against base atli (4f69c29e4348cfeeedd2c5ae44af7a66743834d4).

New 1 · Carried 2 · Cleared 0 · Verified 0 since round 063ecb3

Not shown inline

These findings are listed here rather than on a line of this pull request: some have no line to attach to, and advisory ones are never threaded. Each row says which.

• packages/client-runtime/src/pullRequestQuery.ts:70 — Inherited Object.prototype members pass the undefined guard and are assigned as filter values even though they are not supported enum values. The query token is also removed from the remaining text. — no source location

Standing summary: open

Review details

Completed reviewers:

• architecture (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• architecture (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• architecture (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• frontend (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• security (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• testing (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• testing (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)
• testing (hub-dispatch-v2:codex:gpt-6.1-sol:medium:9441865e1d0f674b)

[atli-skald]

The new iOS implementation sends only option.label to UISegmentedControl and drops option.accessibilityLabel; the previous shared implementation applied that label to each accessible press target.

This finding is advisory tier: a code fix is optional and it does not block the merge on one, but an answer is required before merge — addressed, disputed, deferred, or duplicate.