Notification controls pared back as Mac bootloader migration reaches edge

01Notifications return to a simple Do Not Disturb toggle

dhh authored and merged two changes into quattro removing notification snoozing, screen-sharing detection, the notification panel and its preferences. In omacom/omarchy#16429:issuecomment-6371608347, dhh said the feature had not reached the level of fidelity he considered good enough. These are development-branch changes, not an announced stable release.

omacom/omarchy#16430 leaves the bell as a Do Not Disturb toggle. Notifications use fixed rules: follow the focused display, step aside for fullscreen windows, retain a day of history capped at 100 entries, and allow verification codes through Do Not Disturb. Right-click dismisses cards, while Super+Shift+Alt+, can still bring recorded notifications back on screen.

02Mac bootloader migration publishes to edge with hardware qualification pending

maralcbr merged chriskearney's omacom/omarchy-pkgs#1513, moving m1n1-aurora to pinned omacom/m1n1 source and replacing downstream aura and m1n1-neo packages. github-actions[bot] reported version 1.6.1.aurora20-3 live on edge for aarch64 in omacom/omarchy-pkgs#1513:issuecomment-6359746568. This is an edge publication, not rc or stable qualification.

Review changed the upgrade path before merge. maralcbr switched to a virtual U-Boot dependency so existing installations can keep their provider, expanded the retained Stage 1 boot matrix, and reported that the coordinated image-builder switch had landed. Ordinary package updates change Stage 2 without enrolling a new Stage 1.

scottjones reported a successful scratch-root package migration but raised encrypted M3 Air display failures and a Stage 1 relocation concern in omacom/omarchy-pkgs#1513:pullrequestreview-5624139147. The proposal records hardware qualification as pending for the exact package; a successful build and edge publication do not establish those cold-boot results.

03Installer CI expands to ten installation variants

emirb merged omacom/omarchy-iso#238 into the F1 development branch f1/17-receive-path-archinstall-45. It builds the ISO once and distributes it across ten x86_64 variants covering encryption, UK keyboards, small disks, low memory, BIOS, unified kernel images and a slow installation medium. The default and encrypted variants run the full integration scenario set.

The change moves coverage previously run on a workstation into CI. Known factory-reset failures remain visible and are allowed only by exact assertion text and an expiry date. greptile-apps[bot] also flagged a local harness cleanup problem in omacom/omarchy-iso#238:discussion_r4359256431: a failed VM launch with keep-running can leave fake PCI servers alive. The supplied review described that finding as non-blocking.

04Prebuilt root-image installation remains under review

emirb's open omacom/omarchy-iso#216 would install a prebuilt root image and add machine-specific packages instead of extracting roughly 940 packages during installation. The landing proposal credits hegjon's root-image design. github-actions[bot] reported passing VM installations of 41.6 seconds on x86_64 and 23.8 seconds on aarch64, with longer ISO build times, in omacom/omarchy-iso#216:issuecomment-6364126768.

hegjon posted an automated review with some findings spot-checked by hand, including machine identity initialization, additional kernel boot images and shrink-fallback handling. Later, greptile-apps[bot] flagged a package-count lookup still requesting stock linux rather than the selected image kernel in omacom/omarchy-iso#216:discussion_r4359565646. These are review findings at particular revisions; the passing VM report does not establish that every concern is resolved. The landing PR remains open.

05Web-app icon protection advances through redirect and IPv6 fixes

hizawye's open omacom/omarchy#16343 restricts automatically discovered icons to the final page origin and checks redirects before requesting their destinations. During the discussion, hizawye added bounded page reads, final-page-relative icon resolution and credential retention limited to the same scheme, hostname and effective port. Explicit user-supplied icon URLs retain their existing behavior.

omarchybot reported worker verification of the final reviewed head in omacom/omarchy#16343:issuecomment-6368320917, including 26 focused cases and a real IPv6 server. That followed hizawye's correction of comparisons that had treated IPv6 brackets as patterns. The proposal still awaits a maintainer decision over roughly 250 lines of URL handling and overlap with other icon changes. Its hostname checks are not private-address filtering, and deliberately excluded CDN icons can fall back to Google's favicon.

06Freeze investigation identifies a leaked binder memory-reclaim callback

In omacom/omarchy#15950:issuecomment-6358826873, omarchybot traced reported memory-reclaim freezes to an out-of-tree binder_linux module failing to load alongside the kernel's built-in binder. Its analysis found an error path that leaves a memory-reclaim callback registered after module code is freed. The bot reported three worker hangs after attempting the load and none in three control runs without it, although it could not capture the worker's oops text.

hamedtareqhamed supplied another crash report involving firewall logging. omarchybot explained how freed module memory could make the same defect appear inside different networking functions. jhnct subsequently reported that removing the module stopped the observed oopses in omacom/omarchy#15950:issuecomment-6371695054. The issue remains open, and the investigation explicitly did not explain an earlier sighting on kernel 7.2.5-3.

07Fingerprint removal proposal clears reader storage before local records

scottjones opened omacom/omarchy#16403 to run fprintd-delete while the service and local enrollment records still exist. The current proposal addresses readers that store fingerprints on the device: deleting local records first can leave their device copies unreachable. It also requests sudo before making changes and reports reader deletion failures while continuing removal.

omarchybot reported passing software checks, then requested hardware evidence. scottjones tested the removal order on an M2 Max MacBook Pro and a MacBook Neo and successfully enrolled the same finger afterwards. In omacom/omarchy#16403:issuecomment-6370352605, omarchybot distinguished successful re-enrollment from proof of deletion and asked whether either run showed a warning. The PR remains open; the supplied results establish the tested order and subsequent usability, not confirmed erasure from the enclave.

08Weather radar proposal adds playback for US locations

wesleygrimes opened omacom/omarchy#16406 to show the last ten NEXRAD scans beneath the weather forecast, with playback, scrubbing and times matching the clock format. The proposal enables radar by default, hides it outside NWS coverage, and makes no radar requests when disabled. Opening the enabled panel sends rounded location information to the weather service and requests radar and map tiles from the named providers.

greptile-apps[bot] reported that earlier named-location forecast and keyboard-access findings were fixed in omacom/omarchy#16406:issuecomment-6366926786. wesleygrimes reports full-suite, theme and right-to-left checks. The feature remains an open proposal with a dependency on another PR, rather than shipped radar support.

09NOVA adds coding assistant setup while marketplace verification stays open

Yangass reported successive NOVA releases in the open verification request omacom/omarchy-plugin-marketplace#12377. They add approval-based setup for a local-model OpenCode assistant and profiles for installed Claude Code, Codex and Antigravity launchers. NOVA preserves other profiles, validates launchers and project folders, and leaves the online tools to handle their own sign-in.

Yangass also reported a correction for Ollama 0.40's manifest layout, which had caused valid model installations to fail revision checks. These release and test results are the author's reports. github-actions[bot] recorded Quattro compatibility for the requested 0.17.1 target, but its security baseline still requires manual review. The marketplace snapshot remains unchanged until publication succeeds.

10Plug verification is withdrawn after a clipboard review finding

weedwhitesandwine closed the Plug update verification request and asked for its marketplace listing to be removed. In omacom/omarchy-plugin-marketplace#12459:issuecomment-6358501211, the author accepted the clipboard finding and said they no longer had time to maintain Plug to the standard the reviews required. This establishes withdrawal and a removal request, not completed delisting.

As background from October 22, HANCORE-linux had confirmed an earlier HTTP redirect and peer-owner correction but identified a writable native text field whose automatic clipboard handling could read an unbounded offer into the shared shell. The withdrawal ends this verification attempt without presenting that remaining finding as fixed.