[kylebegeman]

Merges upstream T3 Code v0.1.8-nightly.20261106.4288 into Loom. The seams in docs/fork/seams.tsv survived, the fork's tests and upstream's tests beside the files it changes pass, every package typechecks, and the built web client boots.

Land it from Terminal on your Mac (not inside Loom, which the install quits) with scripts/fork/loom.sh land: it merges with a merge commit, tags loom-v0.1.8-nightly.20261106.4288, publishes the next Loom release and installs it. Never squash or rebase this pull request; the fork needs upstream's history for the next merge.

[kylebegeman]

Review of the unattended resolution: pass.

• Round 1, Linting upstream files the fork edits: REPAIRED
• Round 1, Typechecking apps/server: REPAIRED
  The session changed nothing.
• Round 1, Running the fork's tests in apps/server: REPAIRED
  The session changed nothing.

After review 1:

Earlier reviews failed; a session fixed their findings:

• Review 1: FIXED

I found nothing that needs fixing, so this can merge into main without a person.

The branch holds two upstream merges (4275 and 4288), a clean merge of main and 14 repair and review commits. The 4275 merge had 27 conflicted files; the 4288 merge and the main merge had none. I checked each resolution against upstream's diff from the merge base (e136e8e3d4..6577c6b618) and Loom's diff from the same base to main. I also checked every line that removes a fork: marker between main and HEAD; each marker was moved, re-added on upstream's new code, or dropped because upstream now does the same thing.

The spots that looked wrong but hold up:

• apps/web/src/components/ChatView.tsx: the resolution threw away Loom's whole side of the composer conflict. That's safe because Loom's only change in that block was environmentUnavailable (fleet-connections), and it was reapplied inside upstream's new wrapper.
• apps/server/src/storageCleanup.ts: worker.requestSweep stands in for upstream's requestSweep because Loom restructured the sweep worker. Upstream's real change, the isLive guard on error events, is kept on top of Loom's wider sweep condition, which already includes worktreeOnDelete. The test edits in ea0b33640d only change the expected read counts to match that existing Loom behaviour.
• Mobile SecretRequestCard.tsx: the input-hardening props didn't vanish; upstream moved them into the new SecretTextInput. Loom's vault check still runs before saving, through send.
• apps/server/src/bin.ts → binMain.ts: upstream moved command dispatch into binMain.ts. Loom's runtime-capabilities branch moved with it, and seams.tsv was updated to point there.
• Desktop restart-continuity (DesktopBackendManager.ts, DesktopBackendPool.ts, DesktopApp.ts, DesktopUpdates.ts): the 15 s grace and the provider-cleanup time now sit inside upstream's BACKEND_QUIT_STOP_TIMEOUT, so Loom's separate BACKEND_STOP_TIMEOUT was removed as a duplicate. FORK.md and seams.tsv were updated to match.
• docs/user/telemetry.md: Loom's sentence about the browser app not reading the variable was dropped because upstream now says it. Upstream's new relay-diagnostics section is kept, followed by Loom's note that its builds send no traces.
• Antigravity: 90c1fbf7de changed the client title to "Loom". That would have undone the point of upstream's change, which is to identify as T3 Code to agy. 07de2a1710 restored "T3 Code" and added the line to the brand allowlist.
• Reworded settings text (3c1cdf844c, 97b3f7a839): these edits were needed. Upstream added a lint rule, max-settings-description-length (fix(web): settings descriptions use the full row and stay two lines pingdotgg/t3code#31826), that limits these descriptions.

The other repair commits stay within what their failing check needed:

• a duplicate Queue import removed;
• refreshed renamed to admitted to follow upstream;
• the ws.test.ts mocks adjusted for Loom's project-placement service;
• a loom up brand string in a test;
• the loom.test.ts expectation brought in line with loom.sh, which already runs effect-tsgo;
• a smoke-test fixture for the new service launcher;
• a mobile button swapped for upstream's RecoveryAction.

VERDICT: pass