Upstream nightly v0.0.46-nightly.20261004.2644 conflicts with custom-nightly #41

Merging upstream nightly v0.0.46-nightly.20261004.2644 from main into custom-nightly stopped on conflicts, so no custom build is published until they are resolved. Chamaquita resolves them and, because this issue carries automerge, merges its pull request once every check passes.

Base branch: custom-nightly
Job branch: chamaquita/upstream-v0.0.46-nightly.20261004.2644
Upstream tag: v0.0.46-nightly.20261004.2644 from https://github.com/pingdotgg/t3code.git

Conflicted files:

• apps/mobile/src/persistence/mobile-preferences.ts
• apps/web/src/components/AppSidebarLayout.tsx
• apps/web/src/components/ChatView.tsx
• packages/contracts/src/rpc.ts
• packages/contracts/src/settings.ts
• pnpm-lock.yaml

Task

Before committing the merge, run pnpm exec vp fmt <file>... on the files you resolved. On every attempt, including the first, run the smallest relevant checks, such as changed-file lint or one test file. Fix failures and rerun the affected check before pushing. Spend at most one minute total on focused checks, including their extra tool or dependency setup. Leave checks that exceed that budget or cannot run locally to GitHub CI, and name them in your summary. Never run whole test suites, repository-wide typechecks, or builds locally: GitHub CI runs them on the pull request.

1. Start chamaquita/upstream-v0.0.46-nightly.20261004.2644 from origin/custom-nightly, or continue it if an earlier attempt pushed it. Fetch the tag with git fetch --no-tags https://github.com/pingdotgg/t3code.git tag v0.0.46-nightly.20261004.2644 and merge it with git merge --no-ff v0.0.46-nightly.20261004.2644. Never rebase, squash, or cherry-pick: the nightly decides what is new with git merge-base --is-ancestor v0.0.46-nightly.20261004.2644 HEAD, so only a merge commit keeps the tag an ancestor.
2. Resolve each conflicted hunk:
   • Classify it as disjoint (the sides changed different things, so keep both), same question with different answers (pick one side on the evidence), or superseded (one side's change makes the other's moot).
   • Touch only the conflicted regions, and leave every line git merged cleanly as it is.
   • Keep the fork's customizations and take upstream's changes. The fork's intent is in git log v0.0.46-nightly.20261004.2644..origin/custom-nightly; upstream's is in git log origin/custom-nightly..v0.0.46-nightly.20261004.2644 and its pull requests.
   • Regenerate lockfiles and generated files instead of merging them by hand: take upstream's pnpm-lock.yaml and run pnpm install to reconcile it with the merged manifests.
   • Leave no conflict markers: git grep -nE '^(<<<<<<<|>>>>>>>) ' finds nothing.
3. Commit the merge, push chamaquita/upstream-v0.0.46-nightly.20261004.2644, and open a pull request into custom-nightly. Its body has a table with one row per conflicted hunk and the columns File:lines, Class, custom-nightly, Upstream, Kept, and Why. If a push is refused for the workflows permission, change nothing and finish blocked with that reason.
4. GitHub CI runs the fork's checks on the pull request. Chamaquita merges it as a merge commit once every check passes and GitHub finds it mergeable; if CI fails, Chamaquita hands the failures to the next attempt. The next run finds the tag merged, publishes the build, and closes this issue.

Run: https://github.com/d3labs-dev/t3code/actions/runs/37175555313