chore(coil): merge upstream/main 6524a8d437 (406 commits)

[radroid]

The daily sync has failed three days running (#168): first a red typecheck, then conflicts. This absorbs the 406 upstream commits up to 6524a8d437, in two merges: 371 commits up to 58d253231d on 2026-10-12, then the 35 that landed upstream since.

Land with a merge commit, never squash:

gh pr merge <n> -R radroid/t3code --merge --subject "chore(coil): merge upstream/main 6524a8d437 (406 commits)"

Conflicts

All in the first merge. The second pass (35 commits) merged clean.

• Three retired workflows (mobile-eas-preview.yml, mobile-eas-production.yml, release-desktop.yml): modify/delete, kept deleted per the sync script's policy.
• SourceControlRepositoryService.ts: upstream refactor(contracts): source control provider kind is an open branded slug pingdotgg/t3code#17739 made SourceControlProviderKind an open branded slug and rewrote each "unknown" literal on the lines the fork changes to carry the provider derived from the remote URL (Cloning from Bitbucket fails with an undiagnosable error: "cloneRepository failed for unknown: The source control operation could not be completed" #98). All seven hunks keep the fork's derived provider; resolveCloneProvider now mints the brand, and BitbucketApi comes from upstream's new package.
• pnpm-lock.yaml: seeded from upstream's and re-resolved. The delta is the fork's own importers and security-override pins.

Follow-up commits

• fix(coil): upstream moved source control into @t3tools/source-control-* packages. Fork-owned cloneDiagnostics.ts and SourceControlProviderDiscovery.test.ts still imported the old in-server paths, which was the typecheck failure that opened [coil-sync] daily sync needs attention (verify-failed) #168.
• docs(coil): seam ledger re-baselined. 65 files, +1106/-5833.
• docs(coil): ledger repointed at 6524a8d437. The second pass moved no seam, so the totals are unchanged.

Seam review

Every fork edit in an upstream-touched seam is intact. SourceControlProviderDiscovery.ts was renamed to packages/source-control-core/src/server/discovery.ts; git followed the rename and the fork's spawn-error classification applied unchanged. Upstream did not absorb any fork feature this range, so nothing was removed. Marketing had two commits (header wordmark, user count), nothing worth porting to apps/coil-home.

Second pass: upstream touched three files the fork also edits. DesktopPreReadyPlatform.test.ts keeps the fork's T3 Coil (Alpha) assertion, pnpm-workspace.yaml takes upstream's allowBuilds bump beside the fork's override pins, and pnpm-lock.yaml installs with --frozen-lockfile. No marketing commits.

Verification

Run locally on macOS arm64 under Node 24:

• vp run typecheck: green
• vp run lint: green
• Web tests: 487 files, 6795 tests passed
• Non-web tests: 29 of 30 packages green. apps/mobile has 2 failing macOS-only Swift tests (notification-center-manager.test.ts, permissions-service.test.ts). They compile upstream's native sources with the host swiftc (Swift 6.4 / macOS 27 here), the fork is byte-identical to upstream in apps/mobile/scripts and patches/, and they do not run on the Linux CI runners. Not investigated further; coil-ci.yml is the arbiter.

Closes #168 once landed (the issue needs closing by hand).

Claude Opus 5.5 via Claude Code in T3 Code.

🤖 Generated with Claude Code