[adampeterhiggins]

What's in this sync

Adds 250 upstream commits beyond the parent sync.

• New features: stopped provider threads can resume natively (feat(server): resume stopped provider threads natively pingdotgg/t3code#36526), and new T3 Connect devices can require approval (feat(connect): require approval for new T3 Connect devices pingdotgg/t3code#36419).
• Fixes: browser tabs respect default zoom and appearance (fix(web): new browser tabs open at your default zoom and appearance pingdotgg/t3code#25874); recovered queued edits retain mentions and context (fix(web): recovered queued edits keep their mentions and context pingdotgg/t3code#36578); notebook traceback frames retain their boundaries (fix(web): preserve saved notebook traceback frame boundaries pingdotgg/t3code#36602); timeline follow survives horizontal table scrolling (fix(web): horizontal table scrolling preserves timeline follow pingdotgg/t3code#24045). Branch switching, worktree restoration, session import, desktop navigation, and mobile routing also receive fixes.
• Provider and internal changes: Cursor reports context fill and usage (fix(provider-cursor): Cursor threads report token usage and context fill pingdotgg/t3code#36323), Pi async workflow members appear as subagents (fix(pi): async pi-subagents workflow, chain and parallel members show as subagents pingdotgg/t3code#36599), ACP history reopening avoids per-chunk copies (perf(acp): long ACP threads reopen without per-chunk history copies pingdotgg/t3code#23724), and client subscriptions recover on healthy connections (fix(client-runtime): recover subscriptions that stop on a healthy connection pingdotgg/t3code#24400).
• Remaining commits: usage/account corrections, bounded browser requests and cancellation, file search and checkpoint fixes, composer/markdown corrections, mobile layout and navigation fixes, provider update compatibility, release-manifest validation, and focused test repairs.

Discord announcements were not used: the channel returned only older non-crosspost messages, with no announcement matching this range.

Stack and scope

Parent: #577. This PR adds only newer upstream commits relative to that parent. Merge the parent first.

Base: 29270c6bb3e8e199a66129d8e5efbb2b6a79d8fd.
Pinned upstream: 4574c6013d52867878038967297a885f1692383c.
Range: 29270c6bb3e8e199a66129d8e5efbb2b6a79d8fd..4574c6013d52867878038967297a885f1692383c.

Conflict resolutions

• Web: retained fork composer context/account actions, sidebar tabs, detached/quick-message surfaces, elapsed timers, shared themes and terminal ANSI roles; integrated upstream WSL drops, model selection, compaction history, timing, image galleries and custom CSS. Theme sharing now serializes CSS.
• Desktop/mobile: retained fork startup/appearance and quick-message setup, organisation facets, object/Google links and shared themes while adopting upstream bootstrap, path conversion, reference definitions and reply behavior.
• Server: kept linked checkouts, subscription guards, integrations, custom editors, cleanup and browser deadlines while integrating native resume, provider query policies and diagnostics. Both sides' independent tests retained; setup tests adapted to the fork shell wrapper.
• Cursor: retained Keychain/file credentials and timeout diagnostics beside upstream cached API/team membership discovery; combined context-fill reporting with validated cumulative billing and subscription limits, converting streamed cache counts to avoid double counting.
• Contracts/shared: unioned theme sync, default appearance, access scopes, model-call usage, desktop bridge methods and shared exports. Theme publish/unpublish share the upstream apply semaphore and CSS validation.
• Reviewed upstream refactors for split-file feature loss; none of the conflicted files required porting fork features into a new split file. Reconciled the fork differences guide for upstream Cursor context/usage support.

Verification

• Dependency install completed (vp install, bootstrapped through npm exec because vp was initially absent).
• Contracts, provider-core, provider-cursor, web, mobile, desktop and server typechecks pass.
• Root-focused tests: 114 passed; final theme tests: 12 passed including shared CSS refusal.
• Web-focused tests: 397 passed. Desktop/mobile/Cursor-focused tests: 175 passed.
• Server: broad adapter/orchestration batch had 839 passing cases; final setup/restart 38 passed, preview mocks 8 passed, capability probe 4 passed with one platform skip.
• Resolved-file formatting/lint and git diff --check pass.
• check:changed: format, lint, both knip passes, both generated GraphQL checks, unused patches and all 41 package typechecks passed. Its aggregate test step was stopped because it initializes headless browser fixtures even when browser files/projects are excluded. The focused tests above passed; the aggregate test gate is incomplete under this run's browser-automation restriction. No interactive browser/computer verification was performed.

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

Model: gpt-6.1-sol. Harness: Codex in T3 Code.