[cursor]

What changes

Upstream quattro moved past omacom#18309 (c40eca98b), which is what #120 merged. Thirty-seven commits replayed onto current quattro, through f428bb4fe (merge of omacom#18378). No merge commits. One upstream commit was empty once the earlier deletion was in place, so it was not replayed: 991e73851 only put plans/remote.md back the way Moonlight had found it, and "Remove the remote plan" had already deleted that file. Upstream's tip does not have it either. Two conflicts, both kept the fork's behavior and took the upstream change. Fork delta vs f428bb4fe is the same 256 paths as quattro vs c40eca98b. On the 199 paths upstream did not touch, the added and removed lines are unchanged. Face, Grok Bot, Cursor, linux / linux-headers, and the dropped Claude and translation-sync workflows stay.

• Files replaces Nautilus (Replace Nautilus with Files omacom/omarchy#18378). The file manager is now Files (folio). New installs get it, and migration 1794330979 installs it on existing machines, rewrites org.gnome.Nautilus.desktop to folio.desktop in ~/.config/mimeapps.list (following a symlink), retargets a dock pin from org.gnome.Nautilus to folio, and drops Nautilus, nautilus-python, nautilus-dropbox, and Sushi.
• New installs edit in Plain (Start new installs with Plain as the default editor omacom/omarchy#18398). Setup > Default > Editor offers Plain, and text files open there. Existing installs keep Neovim: migration 1794341736 saves nvim when no editor was chosen, and writes Neovim as the default for text types the user has not already set, including a choice that lives only in ~/.local/share/applications/mimeapps.list. Without a display, Plain falls back to vi, which every install already has. Vim was added for that fallback and then removed again.
• Moonlight is no longer on every install (Move Moonlight from a default install to Install > Gaming omacom/omarchy#18397). It leaves the base package set. Existing installs keep it, and there is no migration. Install > Gaming and Remove > Gaming offer it. The window rule stays for anyone who installs it.
• Qt apps theme through qtengine (Use qtengine for qt theming omacom/omarchy#18325). qtengine replaces the GTK platform theme, so Qt apps use less RAM and take Omarchy's colors. Migration 1792902457 installs it, seeds ~/.config/qtengine/config.json only when the user has none, and the theme templates gain qtengine.colors.
• The agents panel's starters follow a running local model (Open the agents panel's starters on a running local model omacom/omarchy#18357). Theme, plugin, and app starters open on a local model that is up, through the same --prefer-local path as the Quake console, and on the default agent otherwise. Shift-click or Shift+Return keeps the default agent. The tooltip names the local model, and names the default agent while Shift is held.
• A local model that failed links to its logs. A stopped model with an error shows a Show logs link, by mouse or keyboard, opening omarchy-agent-local logs <recipe> in a floating terminal. That includes the other half's log when the model is paired across two Sparks.
• A cabled DGX Spark is offered at the top of the agents panel. When omarchy-local-ai's status says another Spark answers on the ConnectX-7 cable before link setup, the panel shows it the way it shows a recommended model. The button opens link setup in a terminal, which asks for the other machine's password once. The offer stays above the rest of the page.
• Identical notifications collapse into one card again (Collapse identical notifications arriving together into one card again omacom/omarchy#18349). A web app open in several tabs was firing one toast per tab. A new notification that repeats a live card word for word within two seconds takes over that card's slot: one card, one history entry, and the superseded copy is closed at its sender. Same means the same app, source, headline, text, click command, and buttons. The picture is not compared, because Chromium hands each copy its own temporary file. The same words after the window are a second message, and a card on its way out is not brought back by a copy of itself. Unnamed toasts keep their own decks, and different buttons stay on their own cards.
• Omarchy notifications show the sender's glyph. omarchy-notification-send names its app omarchy-action, and that name was resolving to the Omarchy logo ahead of the glyph, so a reminder showed the logo instead of its finger. Anonymous senders name no app, so their name is no longer looked up.
• Dropbox shows sync progress. The panel reports transfer speed and progress, refreshes correctly when a status poll is already running, and leaves Dropbox's staging cache and internal metadata out of recent files and usage scans. Ordinary hidden files stay.
• Gliff can share 1Password. While Gliff is connected, screen-sharing protection is lifted for every window, so 1Password can be shared. The capture override survives the remote service being replaced.
• The ASUS ProArt PZ13 gets speakers and microphones (Support the ASUS ProArt PZ13's speakers and microphones omacom/omarchy#17970). The HT5306QA (Snapdragon X Plus) has no sound card without a board-named topology that linux-firmware does not carry. Setup and migration 1794017822 install asus-proart-pz13-audio. A later user's migration finds the package already installed and does not ask for another reboot.
• The ASUS Vivobook S 15 shows the disk unlock prompt (Show the disk unlock prompt on the ASUS Vivobook S 15 omacom/omarchy#17352). The S5507QA (Snapdragon X Elite) left the panel black at unlock because the display driver waited for the USB-C DisplayPort chain, which loads only after unlock. The display, panel, USB-C chain, and Adreno microcode now load in the initramfs, as on the Yoga Slim 7x and Surface Pro 11. Migration 1793620666 applies that to existing S 15 installs and rebuilds the boot image once. The X Plus model shares the family name, uses another device tree, and is left alone.
• A Snapdragon UKI takes linux-omarchy's own device trees (Take linux-omarchy's device trees before another linux-omarchy kernel's omacom/omarchy#18317). The trees came from the first /boot/dtbs/linux-omarchy*/qcom folder, and linux-omarchy-<name> sorts before linux-omarchy. With a second kernel installed, every boot image got that kernel's trees. linux-omarchy's folder is now named ahead of the pattern, including where the Surface Pro 11 finds its tree.
• An autostarted herdr server starts in its own session. The server is launched with its own session id so it is not tied to the session that started it.
• The remote-desktop plan is gone. Gliff shipped as Omarchy's remote desktop, so plans/remote.md is removed. A short-lived rewrite of that plan landed and was deleted in the same import.
• Translations through Update translations omacom/omarchy#18403, including the new Plain, Files, Moonlight, Dropbox, and agents-panel strings.

The agents panel conflict kept the fork's shownProviders list (hidden providers stay hidden) and took upstream's Shift modifier on starters and the Show logs row. The logs row indexes shownProviders, matching the rest of that loop.

Verification

• Cherry-pick of the 37 commits from 13f4592d2 through 11be9726f applied onto quattro 57af365e4. shell/plugins/agents/Panel.qml conflicted twice and was resolved as above. plans/remote.md was already deleted when Moonlight's edit and its revert arrived; the revert was empty and was skipped. git diff --name-only of HEAD vs upstream f428bb4fe is the same 256 paths as quattro vs c40eca98b. On the 199 paths upstream did not touch, the added and removed line counts match. The other 57 paths are a clean three-way merge of the fork delta with upstream, apart from the Panel.qml resolution. linux and linux-headers are still in the other-packages list. Face, Grok Bot, and Cursor are still in the menu. The Claude workflows and the translation-sync workflow are still absent.
• bash test/shell.d/agents-panel-test.sh passed, including local-model offers, hidden offers, and the panel's sign-in and limit-window helpers.
• bash test/shell.d/default-agent-test.sh passed, including --prefer-local opening the running local model and the usual agent otherwise.
• bash test/shell.d/default-apps-test.sh passed, including editor defaults installing missing editors and selecting an editor that is already installed.
• bash test/shell.d/command-operand-boundaries-test.sh passed, including launch-editor defaulting to Plain, running it inline for $EDITOR, and using vi without a display.
• bash test/shell.d/dropbox-test.sh passed, including transfer progress, a queued refresh, and excluding internal metadata and cache while retaining ordinary hidden files.
• bash test/shell.d/notifications-test.sh passed, including the notification policies (duplicate collapse, and the omarchy-action glyph no longer resolving to the Omarchy logo).
• bash test/shell.d/hardware-quirks-test.sh passed (6), including the Vivobook S 15 writing its initramfs drop-in on that DMI name and the ProArt PZ13 installing asus-proart-pz13-audio only on that machine.
• bash test/shell.d/snapdragon-hardware-test.sh passed (3). bash test/shell.d/surface-pro-11-hardware-test.sh passed.
• Could not run remote-session-service-test.sh (it needs quickshell and grim) or boot a Vivobook S 15, a ProArt PZ13, or a cabled DGX Spark, so the unlock prompt, the PZ13 audio, and the Spark offer were not checked on hardware. No other sync was open.

Screenshots

No visible change: this checkout has no Omarchy session, so nothing was drawn here. Files replacing Nautilus, Plain as the editor, the agents panel, Dropbox progress, and notification cards are visible on a machine; the tests above cover the behavior that can run here.