chore: merge upstream nightly v0.0.43-nightly.20260925.2251 into custom-nightly

[chamaquita-d3]

Fixes #11

Merges upstream nightly v0.0.43-nightly.20260925.2251 into custom-nightly as a merge commit, so the tag stays an ancestor. Four files conflicted. Each resolution keeps the fork's customization and takes upstream's change.

File:lines	Class	custom-nightly	Upstream	Kept	Why
apps/desktop/src/updates/DesktopUpdates.test.ts:90-130	Disjoint	New test: a background check that finds an update downloads it right away (171a820)	New test: Linux .deb installs update, and other non-AppImage installs stay disabled (pingdotgg#13575)	Both tests	They test different behavior, and the merged makeHarness supports both option sets
apps/web/src/components/CommandPalette.tsx:569-581	Disjoint	backgroundEditor.toggle shortcut handler	usage.open shortcut handler that goes to /usage (pingdotgg#9434)	Both handlers; usage.open also closes the sidebar usage panel	The two commands are independent. Closing the panel matches the fork's palette "Open usage" item, which closes the panel before showing the full page
apps/web/src/components/sidebar/SidebarChrome.tsx:27-29	Disjoint	Imports SidebarFooterExtras and useSidebarPanelStore	Imports isSidebarUtilityPage and useNavigateToMainApp	All imports	Each side's code needs its own imports
apps/web/src/components/sidebar/SidebarChrome.tsx:176-181	Superseded (in part)	Back closes the sidebar panel first, then uses canGoBack/history.back(); shows Back when sidebarPanel !== null || currentFooterPage	Back goes to the last main-app URL through navigateToMainApp(); currentFooterPage becomes isOnUtilityPage (pingdotgg#13516)	The fork closes the panel first, then upstream's navigateToMainApp(); Back shows when sidebarPanel !== null || isOnUtilityPage	Upstream's main-app navigation replaces the fork's history-back fallback. The fork's sidebar panel is separate from that and stays
docs/user/usage.md:3-13	Disjoint	"Check usage at a glance" section on the sidebar usage panel	Intro on opening Usage with mod+u and the usage.open keybinding	Both. The upstream intro now says the full page opens from the sidebar usage panel	In this fork, the sidebar button opens the panel, not the page

pnpm-lock.yaml merged without conflicts. Upstream's copy was taken and pnpm install reconciled it. The result is byte-identical to custom-nightly's lockfile.

A second commit, 3bdcded56, adds .js extensions to two relative imports in packages/shared/src/customBackgroundBrightness{,.test}.ts. These are fork-only files from recent commits. Without the extensions, pnpm run typecheck fails with TS2835, and the merge did not cause that.

Checks

Check	Result
pnpm install --frozen-lockfile	✅ passed
pnpm run typecheck	✅ passed (after 3bdcded56)
pnpm exec vp fmt --check	✅ passed
pnpm exec vp lint on resolved files	✅ no errors. CommandPalette.tsx has 3 set-state-in-effect warnings, all outside the resolved hunks. usage.md isn't linted
pnpm exec vp run --filter t3 test	✅ 5382 passed, 10 skipped (see note)
pnpm exec vp run --parallel --concurrency-limit 2 --filter '!t3' --filter '!@t3tools/monorepo' test	✅ passed
pnpm run build:desktop	✅ passed

Note: the job sandbox gives processes every capability, including CAP_DAC_OVERRIDE, so chmod 000 blocks nothing. On the first run of the t3 suite, 7 tests failed, all of them expecting permission-denied errors: cli/theme, keybindings, server, and terminal/Manager. With capabilities dropped (setpriv --bounding-set=-all --inh-caps=-all --ambient-caps=-all), both test commands pass in full, and the numbers above come from those runs. CI runners don't have this capability, so they are unaffected.

Merged by Opus 5.5 (Claude Code) for Chamaquita.

🤖 Generated with Claude Code