chore: merge upstream nightly v0.0.43-nightly.20260927.2344

[chamaquita-d3]

Fixes #24

Merging upstream nightly v0.0.43-nightly.20260927.2344 into custom-nightly stopped on conflicts in five files. This PR is a --no-ff merge of the tag, so the tag stays an ancestor. Every conflict was disjoint, so each one keeps the fork's customization and upstream's change together.

File:lines	Class	custom-nightly	Upstream	Kept	Why
apps/web/src/components/NoProjectsHero.tsx:5-9	disjoint	imports CustomBackground (background picture)	imports isElectron for the draggable desktop titlebar strip (pingdotgg#13713)	both imports	Each import backs a different change in the file, and both changes merged cleanly.
apps/web/src/components/chat/ComposerSurface.tsx:16-26	disjoint	glass surface is var(--glass-surface), with the dark/theme glass-surface overrides removed	max-w-3xl → max-w-(--chat-max-width) for the chat width setting (pingdotgg#11594)	the fork's lines with max-w-(--chat-max-width)	Upstream only changed the max width and the fork only changed the surface variables.
apps/web/src/components/chat/MessagesTimeline.tsx:1256-1260	disjoint	overflow-x-clip → [contain:inline-size] (glass surfaces)	max-w-3xl → max-w-(--chat-max-width) (pingdotgg#11594)	max-w-(--chat-max-width) [contain:inline-size]	Different classes on the same line.
apps/web/src/components/settings/SettingsPanels.tsx:657-662	disjoint	adds activeCustomBackgroundId, customBackgroundEnabled to the restore-defaults dirty check	adds chatWidth (pingdotgg#11594)	all three	These are independent settings. The reset block below already merged cleanly with all of them.
apps/web/src/routes/__root.tsx:32-36	disjoint	imports MascotMoodCoordinator (Dock cat)	imports QueuedMessageSender (pingdotgg#13764)	both imports	These are independent root coordinators.
apps/web/src/routes/__root.tsx:238-242	disjoint	mounts <MascotMoodCoordinator />	mounts <QueuedMessageSender />	both	Same as above.

pnpm-lock.yaml merged cleanly. I regenerated it from upstream's lockfile with pnpm install --lockfile-only, and the result was identical to the auto-merged file. I ran vp fmt on the resolved files. Nothing else was run locally; checks run in CI.

Follow-up: Usage keybinding order (attempt 2)

CI's Test check failed in KeybindingsSettings.logic.test.ts ("orders Usage bindings and command choices like the page"). The comparator from upstream pingdotgg#10158 compared Usage page commands by page order but usage.open by name, so it was not transitive. Where usage.open ended up depended on the input, and the fork's extra default bindings (backgroundEditor.toggle, composer.dictate) moved it. The Usage page commands now sort as one block, in page order, where the first of them would sort by name, so the order no longer depends on the input. The test now expects usage.open after that block.

Resolved by Claude Opus 5.5 in Claude Code (Chamaquita jobs t3code-24-1 and t3code-24-2).

🤖 Generated with Claude Code