[tebiggs]

Merge this with Create a merge commit, not squash, so upstream history stays intact.

Merges upstream v0.1.6-nightly.20261030.3917 into the fork's main. Two files conflicted, both from upstream's "switch your whole fleet between Stable and Nightly" work (pingdotgg#26288).

Conflicted files

• packages/shared/src/cliRelease.ts: kept upstream's new imports and kept CLI_RELEASE_REPOSITORY pointing at tebiggs/t3code (fork feature feat(fork): servers and clients update from the fork's releases #2).
• apps/web/src/state/npmRelease.ts: kept upstream's npmReleaseAtom and its derived npmReleasePublishedAtom, but the atom now reads this fork's GitHub releases instead of registry.npmjs.org. An exact version uses the release tag URL, as the fork's published check already did. nightly and latest use the newest matching release on the first page of the release index, which is enough because the fork keeps only a handful of releases.

Behavior to check

• The fork publishes no npm manifest, so databaseMigration is always undefined. The fork publishes only nightlies, so Switch to Stable finds no release and the dialog says it could not find one "on npm". That wording comes from upstream's UpdateTrackSwitchDialog.tsx, which I left alone.
• Without this change the dialog would have offered upstream's npm version, which the fork's release host does not have.

Verification

• Typecheck passes for shared, web, server and mobile.
• npmRelease.test.ts (new dist-tag case) and cliRelease.test.ts pass.
• The server tests for the auto-merged fork fix(server): background work an agent waits on survives settles, crashes and failed wakes #14 code pass: ThreadSettlementService, ThreadManagementService, ProviderSessionManager, ClaudeAdapterV2 and runtimeLayer.

Done with Claude Opus 5.5 in Claude Code.

🤖 Generated with Claude Code