chore(sync): merge upstream main through 7ac952c630, plus Home, task graphs, dictation, ghost text and ten Android PRs

[eyeveil]

Upstream sync

Merges pingdotgg/t3code main through 7ac952c630 (556 commits). Fork features preserved: account fallback, provider login RPCs, mirrored custom models, Android APK release profile, desktop download routing, migration numbering (V2 starts at 56 here; FIRST_V2_MIGRATION_ID 56).

Notable upstream features landing: delegated tasks in their own worktrees, guided PR reviews and review guides, per-project provider toggles, renaming built-in models, OpenTelemetry export settings, T3 Code as default macOS browser with passkeys, JetBrains over SSH, in-thread message search, Muse Code native provider, GitCafe, SQLite reader worker and non-blocking checkpoints, Enriched mobile markdown (replaces nitro-markdown; fork patch dropped).

Upstream PRs carried ahead of upstream (each its own merge commit)

• feat(home): add Home, an agent that manages threads across your machines pingdotgg/t3code#15975 Home agent (t3dotgg). Thread links keep upstream's t3-thread://v1/<threadId> form with an optional ?environmentId= suffix for other machines, instead of the PR's path segment. Home handlers go through upstream's McpToolAccess checks.
• feat: task graphs for parallel agent work across worktrees and machines pingdotgg/t3code#17930 task graphs. Migration lands as fork id 64 (063_TaskGraphs.ts).
• feat: dictate into the composer with a local speech model pingdotgg/t3code#19273 local-model dictation (sherpa-onnx). DictationError added to runServer's explicit error type.
• feat(claude): suggest the next prompt as composer ghost text pingdotgg/t3code#17618 Claude next-prompt ghost text. Needed apps/server/src/server.ts to spell out runServer's error/service types and bind Ws.layer to wsLayer: the fork's RPC group is now large enough that the checker collapsed it to any.
• Android: feat(mobile): Android foldables swap the rail and floating buttons for a sidebar header pingdotgg/t3code#19424 foldable sidebar header, fix(mobile): Android no longer freezes when you go back from a running thread pingdotgg/t3code#19292 back-navigation freeze, fix(mobile): huge turn diffs no longer run Android out of memory pingdotgg/t3code#19240 huge-diff OOM, fix(mobile): long commands no longer freeze Android work-log taps pingdotgg/t3code#19238 work-log tap freeze, feat(android): configure subscription usage widgets pingdotgg/t3code#17890 subscription usage widgets (widget screen ported to ListRowLayout), fix(mobile): Android review diff scrolls to the end of long lines pingdotgg/t3code#19431 review diff scroll, fix(mobile): Android tablets launched in landscape open full screen pingdotgg/t3code#18634 landscape tablets, fix(android): preserve chat back stack in the PR viewer pingdotgg/t3code#18839 PR viewer back stack, perf(mobile): transfer and paint dirty Android terminal rows pingdotgg/t3code#17195 terminal dirty rows, fix(mobile): restore lost iOS race fixes and Android keyboard parity pingdotgg/t3code#15030 iOS race fixes and Android keyboard parity (keeps the fork's cycleHost shortcut).

Follow-ups outside conflict hunks

Fork modules now import PtyAdapter and HostProcess from @t3tools/shared, the Pi extension reads runtime instructions from provider-core, randomUUIDv4 is called as a method, upstream's new Migrations.test.ts uses fork ids, tests for the removed legacy providers settings map are dropped, and Sqlite.test.ts tolerates the sampled ANALYZE estimate (the extra migration row moved it from 100 to 98).

Verification (local, macOS)

• pnpm typecheck: clean across 32 packages.
• Touched tests: 754 pass. Mobile: 375 pass; pnpm lint:mobile clean (ktlint/swiftlint not installed locally, so the Kotlin change in fix(mobile): restore lost iOS race fixes and Android keyboard parity pingdotgg/t3code#15030 is compiled only by CI).

Supersedes #9 if that branch is no longer needed.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[greptile-apps]

Confidence Score: 4/5

[High impact] Large upstream merge with build, workflow, and dependency changes.

Cancellation on another machine can still leave an agent running, so this PR needs another fix before merging.

Findings

1.  Cancelled agents still start ▶

Fix with agent prompt

### Issue 1
apps/server/src/taskGraph/TaskGraphService.ts:893-896
`advance` saves nodes as running, releases the lock, then launches them without checking their current state. If the user cancels before a launch creates its run, `stopNodes` has no active run to interrupt. The pending launch then starts an agent for a node already marked cancelled, allowing more file changes and paid account use.

Coordinate launch and cancellation so cancellation also stops pending launches.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The follow-up adds cancellation checks around task launches and replays unfinished launches after restart.

• Home can work across the environments connected to a desktop server.

_{Reviews (2) · Last reviewed commit: "fix(server): stop task graph nodes cance..." · Reviewed by Greptile}

[greptile-apps]

Cancelled agents still start

advance saves nodes as running, releases the lock, then launches them without checking their current state. If the user cancels before a launch creates its run, stopNodes has no active run to interrupt. The pending launch then starts an agent for a node already marked cancelled, allowing more file changes and paid account use.

Coordinate launch and cancellation so cancellation also stops pending launches.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/server/src/taskGraph/TaskGraphService.ts
Line: 879-882

Comment:
**Cancelled agents still start**

`advance` saves nodes as running, releases the lock, then launches them without checking their current state. If the user cancels before a launch creates its run, `stopNodes` has no active run to interrupt. The pending launch then starts an agent for a node already marked cancelled, allowing more file changes and paid account use.

Coordinate launch and cancellation so cancellation also stops pending launches.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[eyeveil]

@greptileai review — e507e60 addresses both findings (cancel during launch now stops the launched thread; restart replays a cut-off launch with its original command ids). Please re-review the new head.