chore: sync upstream through 1451e7cb23

[adampeterhiggins]

The fork was 762 upstream commits behind. This merges upstream/main at 1451e7cb23 (range e3b35d1b24..1451e7cb23) into the fork, keeping upstream history and fork behavior. It then merges current origin/main. The parent sync, #332, merged while this run was in progress, so this PR targets main directly.

Conflicts

128 files conflicted: 70 in web, 26 in server, 21 in mobile, the rest in packages and docs. Most were resolved by keeping both sides. These are the notable decisions:

Upstream API moves the fork followed:

• providers moved off EnvironmentServerConfig. Fork components now read useEnvironmentProviders() / providersIgnoringCheckedAtAtom.
• useUpdateClientSettings became updateClientSettings().
• @t3tools/client-runtime gained a pullRequestLinkProject helper, which replaces the fork's own resolver.

Upstream test changes:

• Upstream dropped react-test-renderer and moved React tests to real-browser *.browser.test.tsx files.
• Fork-only test cases were ported into those browser tests. The fork's react-test-renderer tests became createRoot browser tests.

New upstream lint and React Compiler rules:

• no-manual-memo and a React Compiler coverage test now apply to every web file.
• About 70 fork-only files were rewritten to pass: no useMemo/useCallback, no try/finally, no computed-key destructuring.
• AgentAccessSettings.tsx joins ConnectionsSettings.tsx on the allowRawClientAccess lint override, because it reads session metadata, not an RPC client.

Behavior decisions:

• Start from shortcut: the fork's chat.startFrom moves from mod+shift+b to mod+alt+o. Upstream binds mod+shift+b to threadPanel.toggle, and the fork's later binding was shadowing it. Users who saved the old binding keep it. The docs and docs/fork-differences.md are updated.
• Cursor run errors: these now carry Cursor's own message, as in upstream. The fork's out-of-usage → usage_limit mapping is kept.
• Resource telemetry: upstream fixed the root cause by stopping the Electron-descendant walk at the server. The fork's "unflagged Electron child = backend" fallback is therefore removed. The fork's test was rewritten to the real process layout.
• t3_worktree_handoff: new worktrees always go in the managed directory, as in upstream. path is honored only for the fork's move into an existing worktree.
• ThreadLaunchService:
  • Upstream's guard is restored: no setup progress event without a worktree.
  • Cancelling setup now also interrupts the fork's background branch-name generation.
• Cursor adapter: the fork's steer was added to upstream's new failure-test mock.
• Agent transcript timeline: AgentDetailPanel uses upstream's useIncrementalTimelineEntries.

docs/fork-differences.md was reviewed. The only change it needed is the shortcut above.

Verification

All commands use the repository-local Vite+ runner.

Typecheck: passes for web, server (t3), mobile, desktop, contracts, shared, client-runtime, provider-core and provider-cursor.

Lint: vp check on every file that differs from upstream gives 0 errors and existing warnings only. Formatting passes.

Unit tests:

• Server and packages: focused suites for every conflicted file pass, 2016 tests.
• Web: unit tests next to changed files pass, 135 files and 4407 tests, including upstream's React Compiler coverage test.
• Mobile: src/state and src/features pass, 1634 tests.
• Cursor provider: 139 tests pass.

Web browser tests: all 133 browser test files next to changed code were run one file at a time, and each passes on its own. Two run alone are known to fail on macOS, and both are expected to pass on Linux CI:

• UsageService "discovers Pi history…" also fails on plain upstream on macOS (/private/var realpath).
• CommandPalette.focus "…after leaving the file picker" presses Ctrl+P, which is mod+p only off macOS. It passes with Cmd.

Running several browser files in one process crashes here with a Playwright route.fulfill heap error. No browser or computer-use verification was done, and no release build was run.

Merge with Create a merge commit. It keeps upstream history and the merge base for the next sync.

Model: Claude Opus 5.5 (with parallel Claude subagents), continuing an earlier Codex run. Harness: Claude Code in T3 Code.

🤖 Generated with Claude Code

[adampeterhiggins]

This PR is now up to date with main through 021ddc3 (#334, #335, #337, #338, #339). I merged main into the branch instead of rebasing it, so the upstream merge commit and its merge base stay intact and nothing was force-pushed.

Conflicts:

• fix(web): show one divider when a model switch hands off context #334 (one divider for a model switch that hands off context):
  • ChatView and mobile use-thread-composer-state keep the single-divider logic, written as plain values to satisfy the new React Compiler lint rules. ChatView reuses its existing pendingModelChange.
  • In V2LifecycleRow, the handoff endpoints now show fix(web): show one divider when a model switch hands off context #334's traits next to the fork's account labels, and the model-change row uses item.title.
• fix(server): show workflow member usage and tool calls #335 (workflow member usage and tool calls):
  • Upstream's fix(server): Claude workflow members stream their thinking and tool calls into their threads pingdotgg/t3code#20856 already streams workflow member transcripts, tool calls included, via workflowAgentTranscript.ts. workflowAgentAnswers.ts is gone with it.
  • Only the usage half was ported: claudeWorkflowMemberUsage in ClaudeAdapterV2.ts, plus a test.
  • docs/fork-differences.md is updated to match.
• fix(build): fork builds publish to the latest update feed #337 (fork builds publish to the latest feed): kept both sides' new build-desktop-artifact tests.
• fix(web): pasted pull request comment links find comments posted moments ago #339 (pasted PR comment links find fresh comments): re-applied the fresh activity reread on the hook-free useResolveComposerObjectLink.

Verification:

• Typecheck:
  • Web, mobile, client-runtime and shared pass.
  • The server passes native tsc --noEmit -p apps/server/tsconfig.json. tsc-rs (vp run --filter t3 typecheck) reports about 180 unknown inference errors in cli/*, server.ts and AgentAccessMcpServer.ts. This is a tsc-rs bug: appending any trivial function to packages/shared/src/modelChangeMarker.ts on the previous commit triggers the same errors. Type annotations and splitting the module did not clear it.
• Tests:
  • Shared, client-runtime and server tests for the touched code: 542 pass.
  • Mobile src/state and src/features/threads: 713 pass.
  • Web React Compiler coverage plus V2LifecycleRow: 1180 pass.
  • useResolveComposerObjectLink and MessagesTimeline browser tests pass.
• Lint: vp check gives 0 errors.
• Known failure: build-desktop-artifact "skips the primary native probe for cross-architecture Windows payloads" fails only because the test's arm64 target matches this arm64 Mac.