chore(coil): merge upstream/main 83bbfa7e87 (90 commits)

[radroid]

The daily sync had been failing since 09-21 (issue #156) on conflicts in apps/desktop/src/ipc/channels.ts and pnpm-lock.yaml. This merges upstream 83bbfa7e87: 66 commits, plus a 24-commit second pass that landed upstream while the first was being verified. It lands as merge commits, so the merge-base advances.

Conflicts

• .github/workflows/ci.yml: kept deleted. It is a retired upstream workflow, per scripts/coil/sync-upstream.sh.
• apps/desktop/src/ipc/channels.ts: kept both sides. Upstream's PREVIEW_RECORDING_INPUT_CHANNEL goes above the fork's appended coil update block, so the seam stays +10/-0.
• pnpm-lock.yaml: seeded from the fork's lock and regenerated with --lockfile-only. Every resolved version that moved went up (vite-plus 0.3.0 → 0.3.3, oxlint, oxfmt, @shadcn/lint). The security sweep's pins are unchanged.

The second pass had no conflicts.

Fix made during the sync

• The offline queue now releases the attachment uploads it drops (2041766bee). Queued messages are text-only, so handleQueueComposerSubmission discards the composer's images and files. It never released their uploads. Upstream fix(web): retry failed attachment uploads after reconnect pingdotgg/t3code#10338 now keeps a failed upload alive and retries it on reconnect, and the queue runs mostly while disconnected. So every dropped attachment would have re-uploaded later and left an orphan pending upload. It now goes through releaseDraftAttachments, as upstream's own discard paths do. This is registered in the SEAMS parallel-paths table.

Seam review

• Every code seam kept its exact pre-sync footprint through both passes. Only the retired ci.yml and the regenerated lock moved in the merge.
• The ledger is re-baselined to 78 files, +2557/-5012, against 83bbfa7e87, with churn and risk remeasured. It also fixes stale pnpm-workspace.yaml totals (+23 → +29) that chore(coil): Dependabot runs go green: vendored repos excluded, 38 advisories re-resolved #155 and fix(deps): patch Nanoid zero-size advisory #157 never updated.
• Two read-only reviewers checked the web and the server/contracts/desktop/mobile semantics. No other breaks.
  • Checked and clean: the threadEnvMode export removal, message-sent events without a turnId, t3.json submodule settings, the OTLP settings refactor, and the attachment limit going from 8 to 100.
  • No apps/marketing changes to port to coil-home, and no new upstream workflows.

Verification (local)

• vp run typecheck: all 17 packages pass, including scripts.

• vp run lint: passes, warnings only.

• Tests, run per package:

  Package	Result
  web	415 files / 5652 tests, re-run after the second pass
  server	373 files
  desktop	116 files
  mobile	183 files
  all other packages	pass

  • Server: 9 upstream-owned files failed only because of macOS /var → /private/var tmpdir symlinks. With TMPDIR resolved, all 286 of their tests pass. They are byte-identical to upstream and pass on Linux CI.
  • Mobile: 2 files need swiftc, which this Mac can't run until the Xcode license is accepted.

• Built the desktop and server bundles (vp run --filter @t3tools/desktop --filter t3 build, which includes the web build and its license plugin).

  • Ran the bundle gate's collectRequiredPackages over them. The required native externals are unchanged, and none is excluded by the fork's packaging globs.
  • The full .app was not packaged locally, because the Xcode license blocks clang and iconutil.

Deferred (not sync fixes)

• Undo-archive vs loops. Upstream feat(web): undo settle, snooze and archive, with a mod+z shortcut pingdotgg/t3code#12848 adds a 5 s undo for archive. If the loop supervisor's 60 s tick lands inside that window, loop guard 4 disarms the loop, and unarchiving never re-arms it. This one-way door already existed; undo makes the round trip more likely. The fix is a design decision: pause on a fresh archive instead of disarming.
• Upstream's lint:restyle-ceiling ratchet (chore(lint): report className restyling of components/ui exports pingdotgg/t3code#12982). It is not a fork gate, because it lived only in upstream's ci.yml. Fork UI puts apps/web/src at 635 findings against upstream's ceiling of 628. Recorded in SEAMS.
• Small cosmetic gaps, all present before this sync:
  • Fork queue rows print raw text where upstream's queued rows now render citations (fix(web): render citations in queued messages pingdotgg/t3code#12403).
  • Fork overlays ignore the panel-motion setting.
  • Both overlays use chat-composer-horizontal-inset, a class upstream deleted in August.

Closes #156

🤖 Generated with Claude Code — Claude Opus 5.5 (1M context), running in T3 Code