lyona v2026.10.0-beta.6

lyona 2026.10.0-beta.6

Seventh beta of the Arch Linux line. This is a pre-release: the ISO
workflow publishes every release with --prerelease, and a beta is never
promoted to Latest.

Updates now work end to end. lyona-update checks an update without a false
mismatch, rolls back with the cursor themes, and keeps the shared data where
the system was installed. The panel's popups take the keyboard while a window
is open, and the window overview no longer lists the panel.

Also in this release:

• the image installer times its steps and names the first keys;
• every AUR build goes through one helper, with reviewed pins;
• the desktop starts fewer resident processes;
• Settings and install.sh say more plainly what they do.

CHANGELOG.md has the complete list.

Artifacts

Artifact	Name
Source archive	lyona-2026.10.0-beta.6.tar.gz
Installer image	lyona-2026.10.0-beta.6-x86_64.iso
Checksums	lyona-2026.10.0-beta.6-SHA256SUMS
Signature	lyona-2026.10.0-beta.6.sigstore.json

• The signature signs the source archive and the image. Check the image
  with cosign (docs/src/install.md).
• The installer image carries iso_label=LYONA_2026_10_0_BETA6.

Updates (#280)

Found by a full install-and-update run in a VM:

• No false mismatch. Every lyona-update apply ended with "MISMATCH:
  privileged helper lyona-update-root" and asked you to roll back, after a
  good install. Its check filled in one of the four paths written into that
  helper.
• Rollback works. lyona-update rollback refused its own backup ("a path
  outside the managed install locations: usr/share/icons/..."): the update had
  reinstalled the helper for /usr/local/share.
• The shared data stays put. With PREFIX /usr/local (or /usr),
  make install-system now puts the cursor and GTK themes, the GRUB theme and
  the licenses in /usr/share by default, as install.sh always did, and the
  update helper installs with the paths it was installed with, recorded in
  /etc/lyona-release. Any other PREFIX keeps them inside it.
• Stale copies go. Earlier updates left copies of those themes under
  /usr/local/share, which is searched first, so they hid the current ones.
  The install removes lyona's own copies, only where lyona's license directory
  shows it installed there, and names each one; a theme you installed there
  yourself is kept.
• The reason stays on screen. After a failed update, the panel's popup
  showed "The installed release matches the channel." under "The update did
  not finish"; it now keeps the error.

The desktop

• Popups take the keyboard (#280). With any window open, Escape, the arrow
  keys and typing went to that window, not to the window overview, the
  Control Center, the power menu or the other panel popups. A popup now asks
  for the focus; dwm gives it, and gives it back to your window when the popup
  closes.
• The overview lists windows only (#280), not the panel as a window called
  "quickshell".
• Choosing a window switches to it (#280). Enter in the overview, or a
  click on a running app in the panel, now focuses that window, on its own tag
  too. dwm used to only mark it urgent. An application asking for the focus
  for itself is still only marked urgent, so nothing steals it.
• Each monitor's panel names its own window (#280), where the second
  monitor's said "Desktop".
• Closing a window goes back to the one you were on (#280), not to the
  first tiled window; so does Escape in the launcher and the keybind viewer.
• Windows without a themed icon show the generic icon when the theme has
  one, else the app's initial, instead of an empty button.
• The panel survives a shell reload (#280). An update reloads the shell's
  configuration; its "reloaded" notice was taken for the bar, dwm and the shell
  raised the two over each other without end, and afterwards windows covered
  the panel until the next login.
• Restart Quickshell (Control Center, Super+Shift+R) works from a
  TTY or ssh too.
• Fewer resident processes (#283-#287): Bluetooth and media come through
  Quickshell's own services; Settings > System runs one watcher where it ran
  eight; the panel's state bridge starts about 80% fewer processes when a
  window's title changes; closed popups hold no lists; dwm-status is no
  longer started.
• The volume keys change the output the panel shows, through PipeWire or
  PulseAudio, instead of the ALSA Master control (#278).
• Settings: search finds "shortcut", "hotkey" and "keybind" (#293);
  Appearance > Compositor can let full-screen windows bypass Picom (#288);
  Defaults shows the AppImage handler (#276); Toolkit themes show as applied
  (#274).
• Lock reports failure when nothing locked the screen (#269).
• dwm's runtime configuration (hotkeys.toml, themes.toml,
  window-rules.toml, their reload) moved from dwm.c into config.c
  (#280), with no change in behaviour.

Installing

• The image installer shows how long each step has run, how long it
  usually takes and the newest line of its log (#291), wrapped within the
  screen and lined up with it, and names the first keys to know (#295).
• install.sh leads its summary with what it changes on the system,
  asks about CachyOS just before the confirmation (#294), and ends with its
  warnings (#290).
• The recommended profile adds Thunar and NetworkManager (#292).
• AUR builds (yay-bin, topgrade-bin, the legacy NVIDIA drivers) go
  through dwm-aur.sh, with pinned commits and checksums, built as you within
  a time limit (#281).
• QEMU/KVM installs get the guest utilities again (#310).

Upgrading from 2026.10.0-beta.5

• The update: with lyona-update (or Settings), or from a checkout with
  git pull and ./install.sh.
• The first update runs beta.5's code, once: beta.5's helper does the
  install and beta.5's lyona-update checks it. This release is shaped so
  that check passes. Rollback with beta.5's backup works from this release's
  helper. Log out and back in afterwards, for the new dwm.
• After lyona-update, also run ./install.sh from a checkout, or install
  the new packages yourself (Thunar and NetworkManager in the recommended
  profile). lyona-update installs lyona's own files, not packages.
• hotkeys.toml: bindings still at an earlier release's default move to
  this release's, after a backup; bindings you changed are kept (#273, #278).

Qualification status

Not tested on real hardware. On the build host (Arch with the CachyOS
repositories, x86_64): the full suite, each step on its own, passed on the
release tree; the root-helper tests passed as root in a disposable container.

In a VM (QEMU/KVM, UEFI, standard VGA, no NVIDIA). The image was built three
times as the last fixes landed; each build was installed fresh:

• The release tree's image (SHA-256
  9956f9f10da9bc5d12b88dd9c6edd2ec6a9bced471dd804f3f52686c3144bc32): a fresh
  install (btrfs) reached the desktop, and all 96 desktop checks passed: the
  window functions, tags, closing a window back to the one before it, the
  popups and the overview by keyboard, hot reload of the three configuration
  files, and idle cost. The installer's step status wrapped within the screen.
• The first build (SHA-256
  cd78abbdf455a7688386b1208d34cb2b8b8532eb5328af490a6321f83daba5f4, before
  the close-focus and installer-status fixes): a fresh install (ext4) passed the
  same 96 checks.
• Updates: with this release's code, and from a fresh beta.5 install with
  beta.5's code, apply verified and rollback restored; an install with earlier
  updates had its stale theme copies removed.
• docs/evidence/280-config-split.md has the details.

Not tested yet: real hardware, legacy BIOS, NVIDIA, Wi-Fi installs, two
physical outputs (two monitors were tested as Xinerama screens and RandR
monitors), and a real run of the signing workflow.

lyona v2026.10.0-beta.5

lyona 2026.10.0-beta.5

Sixth beta of the Arch Linux line, and the first since beta.4. This is a
pre-release: the ISO workflow publishes every release with --prerelease,
and a beta is never promoted to Latest.

It fixes three security issues in lyona's update path and root helpers. The
install image now:

• connects to Wi-Fi;
• uses your keyboard layout for the passwords;
• lets you change an answer or retry a failed base install;
• downloads from mirrors near you.

Installs are faster, and the install image goes straight from the boot splash
to the installer. On the desktop, AppImages open without Gear Lever's
runtimes, peripheral batteries are shown, Picom is part of the desktop, time
sync is on, and Firefox is the default browser. Running install.sh again
keeps your ~/.bashrc and your time settings. CHANGELOG.md has the complete
list.

Artifacts

Artifact	Name
Source archive	lyona-2026.10.0-beta.5.tar.gz
Installer image	lyona-2026.10.0-beta.5-x86_64.iso
Checksums	lyona-2026.10.0-beta.5-SHA256SUMS
Signature	lyona-2026.10.0-beta.5.sigstore.json

• The signature signs the source archive and the image. Check the image
  with cosign (docs/src/install.md).
• The installer image carries iso_label=LYONA_2026_10_0_BETA5.

Security

Three advisories, published with this release:

• GHSA-x538-46gg-v37h: the update helper verifies signatures itself.
  • Before: lyona-update checked a release's signature as you, but its
    root helper installed any tarball whose checksum the caller passed, behind
    the routine "install a lyona system update" prompt.
  • Now: the helper checks the signature on its own copy, against lyona's
    release workflow, which is fixed in the helper.
  • Unsigned installs: a release from before signing, or an offline
    --sha256 file, asks through a different prompt that says the signature
    was NOT verified.
• GHSA-xfhv-7h9c-m966: release signing has its own job.
  • Before: the job that builds the image held the signing token.
  • Now: a separate job, which runs none of the repository's code, signs
    what the build made. The build container is pinned by digest.
• GHSA-c897-2mjw-fwhh: the root helpers stay out of your files.
  • The display helper runs as root with root's own HOME, and gets a
    root-owned copy of your X authority, read with your permissions.
  • The System Health helper checks every library its tool loads before
    running it as root.

The update-helper fix takes effect from the update after this one.
Upgrading from beta.4 to beta.5 still runs beta.4's helper, once.

The install image

Wi-Fi (#237)

• The wizard offers Wi-Fi when there is no wired connection and the
  machine has a Wi-Fi card: Connect to Wi-Fi, Retry, or Continue
  without internet.
• Networks are listed strongest first, with signal strength and security,
  plus Other (hidden network). Open and WPA personal networks are
  supported; enterprise (802.1X) and WEP are listed with the reason they
  can't be used.
• The passphrase stays private. It goes only into iwd's own profile, never
  onto a command line or into the install logs. A passphrase ending in =
  keeps it on the new system (#270).
• The new system stays online: it gets a NetworkManager profile for the
  same network.
• A chip with no driver on the image is named. Some Broadcom chips need
  broadcom-wl; install over a cable or USB tethering instead.

Keyboard layout and passwords (#265)

• The layout applies at once. Before, the disk-encryption and user
  passwords were typed in a US layout, and the same keys then gave other
  characters at the LUKS prompt and at login. On a French or German keyboard,
  the disk would not unlock.
• The password prompts name the layout ("Password (keyboard: fr):").
• The list is searchable, with names for the common layouts, then every
  console keymap. Swedish, Turkish and Slovenian now use real keymaps
  (sv-latin1, trq, slovene); before, they were listed as names that
  aren't keymaps.

Going back, and recovering (#266)

• Change an answer: the summary can change any one answer instead of
  cancelling. A new keyboard layout asks for the passwords again.
• Cancel comes first on the summary, so Enter alone never wipes the disk.
• Esc goes back in the timezone and country lists, instead of ending the
  installer.
• A failed archinstall shows the recovery menu (Retry, View full log,
  Exit to shell), with what state the disk is in. Retry runs it again with
  your answers.
• The passwords file for archinstall is removed however the run ends.

Faster installs (#245-#250)

• Mirrors near you: the installer asks to use your timezone's country, or
  another, and ranks those mirrors by speed before downloading. It downloads
  10 packages at a time, up from 5.
• One kernel and one initramfs: linux-cachyos, installed by
  archinstall. There is no fallback image, and grub-mkconfig runs once.
  docs/src/install.md shows how to add linux-cachyos-lts or the fallback
  image back.
• One pacman transaction for every package, the gaming ones included.
• Topgrade comes from the AUR's topgrade-bin, in seconds instead of a
  multi-minute cargo build. No Rust toolchain is installed for it.
• The MesloLGS Nerd Font comes from the repositories (5.7 MiB) instead of
  a 112 MB download.
• Both installers time each step, and the image install's log ends with a
  table of where the time went.

Straight from the splash to the installer

The root console no longer flashes by between the splash and the installer,
and the first screen appears before the network check.

The desktop

AppImages without Gear Lever's runtimes (#260)

• The first open asks. Opening an AppImage (from Thunar, or the browser's
  downloads) asks Add and run, Add only or Cancel, with where it
  was downloaded from. Closing the question cancels, and nothing is moved.
• Adding moves the file to ~/Applications and puts it in the launcher,
  with its own name and icon, read from inside it, never by running it.
• Opening it again just starts it.
• fuse2 and squashfs-tools come with the recommended desktop, so
  classic AppImages run.
• Gear Lever (about 1.7 GB of Flatpak runtimes) is opt-in with
  install.sh --with-gearlever. An installed Gear Lever is kept.

Notifications with buttons (#260)

A notification that comes with buttons shows them, up to three, and stays
until one is pressed or it is closed.

Peripheral batteries (#243)

• Settings > Power lists the batteries of wireless mice, keyboards,
  headsets and controllers that UPower reports, and so does the Control
  Center's power page.
• A coarse level shows as a word. A device that reports only "Full" or
  "Low" shows that word, not a made-up percentage.
• Below 15%, a peripheral sends one notification.

Picom is part of the desktop (#244)

• Required for previews: the overview's window previews need Picom, so the
  recommended and full profiles require it.
• Lean default configuration: no shadows, fading, blur or animations.
• Backend: the backend is chosen for your graphics card.
• When Picom can't start, the desktop still starts and says why once.

Time sync, Firefox and GRUB

• Time sync is on. install.sh turns on systemd-timesyncd when nothing
  else keeps the clock. If you turn it off later, it stays off: running the
  installer again no longer turns it back on (#258, #268).
• Firefox is installed in the recommended and full profiles, and a new
  account gets it as the default browser (#240).
• The GRUB menu no longer lists every firmware boot entry (#239).

install.sh

• The dwm build questions are opt-in (#289). A new config.h uses the
  defaults. --configure-build asks the questions before the summary, and
  asks again when an answer isn't valid. Before, one typo stopped the install
  after the summary.

Fixed

• Running install.sh again no longer throws away your ~/.bashrc
  edits. It updated the mybash checkout, which those files link into, by
  deleting it. Now it updates the checkout in place and leaves it alone if you
  changed it (#267).
• An install no longer fails when the CachyOS repositories are part way
  through a Qt update.

Installing from the image

1. Check the image (docs/src/install.md), write it to a USB stick, and boot
   it, with UEFI or a legacy BIOS.
   • On a Mac, hold Option at startup and choose EFI Boot.
2. The installer starts on its own. Without a wired connection, choose
   Connect to Wi-Fi. Choose your keyboard layout first; the passwords are
   typed with it.
3. Answer the questions. Use Change an answer... on the summary if
   needed, then confirm.
4. When it finishes, read its notes, press Enter, and leave the stick in until
   the screen goes dark.

Upgrading from 2026.10.0-beta.4

• The update: with lyona-update (or Settings), or from a checkout with
  git pull and ./install.sh.
• After lyona-update, also run ./install.sh from a checkout, or install
  the new packages yourself. lyona-update installs lyona's own files, not
  new packages, and doesn't change per-user defaults:
  • fuse2 and squashfs-tools, and the AppImage handler:
    sudo pacman -S --needed fuse2 squashfs-tools, then
    xdg-mime default lyona-appimage.desktop application/vnd.appimage;
  • Firefox, and Topgrade from topgrade-bin;
  • time sync.
• Picom now ships its own lean configuration, used when you have none of
  your own. To keep the package's shadows and fading, copy
  /etc/xdg/picom.conf to ~/.config/picom/picom.conf.
• Topgrade built with cargo stays in ~/.cargo/bin until you remove it;
  install-topgrade offers to...

lyona v2026.10.0-beta.4

lyona 2026.10.0-beta.4

Fifth beta of the Arch Linux line. This is a pre-release: the ISO
workflow publishes every release with --prerelease, and a beta is never
promoted to Latest.

The install image now installs GRUB instead of systemd-boot, so lyona
installs on machines with a legacy BIOS as well as UEFI ones, with the CyberRe
boot menu theme (#235). CHANGELOG.md has the complete list.

Artifacts

Artifact	Name
Source archive	lyona-2026.10.0-beta.4.tar.gz
Installer image	lyona-2026.10.0-beta.4-x86_64.iso
Checksums	lyona-2026.10.0-beta.4-SHA256SUMS
Signature	lyona-2026.10.0-beta.4.sigstore.json

• The signature signs the source archive and the image. Check the image
  with cosign (docs/src/install.md).
• The installer image carries iso_label=LYONA_2026_10_0_BETA4.

What is in this beta

GRUB on legacy BIOS and UEFI

• The wizard installs on a legacy BIOS. It used to refuse any machine that
  booted without UEFI, because systemd-boot is UEFI-only.
  • On UEFI, GRUB goes in the firmware's fallback path,
    EFI/BOOT/BOOTX64.EFI, on an EFI system partition at /boot. Firmware
    that ignores the boot entries other systems write, Apple's among it, still
    boots it.
  • On a legacy BIOS, the disk is MBR, with an ext4 /boot.
  • /boot is never encrypted, as GRUB reads the kernels from it. With
    LUKS, only the root partition is encrypted.
  • The summary says which: Boot: UEFI (GRUB) or
    Boot: legacy BIOS (GRUB).
• The boot menu uses the CyberRe theme.
• linux-cachyos boots by default. It is the menu's first entry
  (GRUB_TOP_LEVEL); the stock Arch kernel stays in the menu as the fallback.
  lyona-cachyos install-kernel --make-default sets this under GRUB too.
• Size and time:
  • the installed system is about 45 MiB larger;
  • GRUB itself adds about a second before its 5-second menu;
  • the install image does not grow.
• Only the bootloader changes. Arch, and so lyona, still uses systemd as
  its init system.

Fixed

• The GRUB theme reaches the menu on UEFI. lyona-grub-theme and
  lyona-cachyos looked for /boot/grub as your user, but a UEFI /boot is
  the EFI system partition, which Arch mounts readable by root only. The menu
  was then never regenerated with the theme. They now look as root. This also
  affected existing UEFI installs that boot with GRUB from /boot.

Installing from the image

1. Check the image (docs/src/install.md), write it to a USB stick, and boot
   it, with UEFI or a legacy BIOS.
   • On a Mac, hold Option at startup and choose EFI Boot. The other
     entry for the stick (often shown as "Windows") boots it in legacy mode,
     which works too, but EFI is the better fit for a Mac.
2. Run lyona-install, answer its questions, and confirm its summary.
3. When it finishes, read its notes, press Enter, and leave the stick in until
   the screen goes dark.

Upgrading from 2026.10.0-beta.3

• Your bootloader is not changed. An existing install keeps the bootloader
  it has. Moving one from systemd-boot to GRUB means reinstalling from the
  image.
• With lyona-update, or from a checkout with git pull and
  ./install.sh, as for beta.3.
• Existing installs that boot with GRUB get the CyberRe theme from
  ./install.sh (or sudo lyona-grub-theme apply CyberRe), now also on UEFI.

Qualification status

Not tested on real hardware, the 2012 MacBook Air included. On the build
host (Arch with the CachyOS repositories, x86_64):

• The full suite (scripts/run-tests) passed on the GRUB change before it
  was merged.
• In QEMU/KVM, from an image built from the GRUB branch (4 GiB, a 30 GiB
  virtio disk, btrfs, no LUKS, no NVIDIA):
  • Legacy BIOS (SeaBIOS): installed with no manual help and nothing on the
    closing screen. It boots the CyberRe menu, then linux-cachyos.
  • UEFI (OVMF): installed, but the theme step skipped the menu: the bug
    fixed above. With the menu regenerated by hand, as the fix now does, it
    boots the CyberRe menu, then linux-cachyos.

Boot time, measured from reset in the VM:

Firmware	Firmware and GRUB, to the menu	Menu	Login screen or desktop	Kernel and userspace
Legacy BIOS	2.1 s	about 5.3 s	11.6 s	3.98 s
UEFI	3.2 s, about 1 s of it GRUB	about 6.3 s	13.7 s	3.90 s

Not tested yet:

• A UEFI install from an image with the fix, to see the theme applied
  without help.
• Real hardware, LUKS on legacy BIOS, ext4, and the NVIDIA drivers under
  GRUB.

Two tests are known to fail now and then without a fault: System Health under
Xvfb ("Control Center popup did not open") and the appearance inventory. Both
print what they saw when they fail.

lyona v2026.10.0-beta.3

lyona 2026.10.0-beta.3

Fourth beta of the Arch Linux line. This is a pre-release: the ISO
workflow publishes every release with --prerelease, and a beta is never
promoted to Latest.

It brings a smaller install image that boots the CachyOS kernel, and fixes for
the desktop session and Settings found after 2026.10.0-beta.2 (#229, #230,
#231). CHANGELOG.md has the complete list.

Artifacts

Artifact	Name
Source archive	lyona-2026.10.0-beta.3.tar.gz
Installer image	lyona-2026.10.0-beta.3-x86_64.iso
Checksums	lyona-2026.10.0-beta.3-SHA256SUMS
Signature	lyona-2026.10.0-beta.3.sigstore.json

• The signature signs the source archive and the image, as in beta.2.
  Check the image with cosign (docs/src/install.md).
• The installer image carries iso_label=LYONA_2026_10_0_BETA3.

What is in this beta

A smaller image that boots CachyOS

• The image is expected to be about 700 MB smaller. It no longer carries
  the desktop's 66 packages, which the live medium never used: the new system
  downloads every package it installs. It keeps only what the wizard runs:
  gum, jq, curl, openssl, pciutils and plymouth.
  • The install itself is unchanged, and takes as long as before.
• Image installs boot linux-cachyos by default. The stock Arch kernel
  stays in the boot menu, as the fallback if the CachyOS kernel does not boot.
  On an existing system, --cachyos-kernel still leaves the default alone.
• The closing screen lists only what went wrong. The GameMode re-login,
  the deferred display setup and the Picom tooltip rule are notes now. None of
  them was a fault.

The desktop session

• Restart Quickshell works. It left no shell at all: the restart ran as a
  child of the shell it stopped, and died with it.
• Your resolution is kept across logins. Keep lasted only for the session
  unless you also chose "Use at next login". The kept layout is applied again
  at login, when exactly the same monitors are connected.
• The wallpaper is redrawn after a resolution or layout change, instead of
  staying drawn for the old size.

Settings

• Settings and System Health open below the panel, which stays visible,
  instead of fullscreen over it.
  • A wider effect: dwm now centers every new floating window in the area
    below the bar. Dialogs open slightly lower and no longer overlap it.
  • Fullscreen windows are unaffected: a window that opens fullscreen
    keeps its monitor's full bounds.
• Settings search finds what each section holds: "weather", "battery",
  "wifi", "timezone" and others found nothing before.
• The weather popup asks for a location when none is set, with a field and
  a Set location button, instead of sending you to Settings.

Installing from the image

1. Check the image (docs/src/install.md), write it to a USB stick, and boot
   it.
2. Run lyona-install, answer its questions, and confirm its summary.
3. When it finishes, read its notes, press Enter, and leave the stick in until
   the screen goes dark.

Upgrading from 2026.10.0-beta.2

• With lyona-update: this is the first update whose signature beta.2's
  lyona-update checks, with cosign. Make sure it is installed
  (sudo pacman -S --needed cosign); without it, the update is refused.
• From a checkout: git pull, then ./install.sh.
• Your resolution: choose it once more in Settings and press Keep. Earlier
  choices were not saved for the next login.
• The CachyOS kernel: existing installs keep their boot default. To boot
  linux-cachyos by default on systemd-boot, run
  lyona-cachyos install-kernel --make-default linux-cachyos.

Qualification status

Not tested on real hardware. On the build host (Arch with the CachyOS
repositories, x86_64):

• The full suite (scripts/run-tests) passed on each branch before it was
  merged.
• In Xvfb under this release's dwm, Settings and System Health open below
  the panel.
• In a throwaway Xvfb session:
  • Restart Quickshell was checked by its test.
  • The wallpaper redraw ran once after a resolution change, and not at
    startup.

Not tested yet:

• The image, built by the release workflow and installed in a VM. That is
  the first test of an image with only six packages over releng, and of
  linux-cachyos booting by default.
• The resolution kept across a real logout and login, and the panel staying
  visible in a real session with Settings open.

Two tests are known to fail now and then without a fault: System Health under
Xvfb ("Control Center popup did not open") and the appearance inventory. Both
print what they saw when they fail.

lyona v2026.08.0-beta.1

First beta of the Arch Linux

• Port the entire distribution target from Fedora to Arch Linux: the
  installer, dependency map, and diagnostics now use pacman and Arch
  package names; the Fedora Kickstart/RPM Fusion/COPR image path is replaced
  by a best-effort archiso-based install medium
  (scripts/build-lyona-arch-iso.sh); an AUR helper (yay) is installed
  as a standing convenience tool. Project branding moves to
  technicks89/lyonasoft.com. Arch Linux is now the sole supported
  platform.

• Rename the project from dwm-titus to lyona, to avoid confusion with
  the original Fedora-based dwm-titus project this was forked from.
  Renames the compiled-in XDG config/data subdirectory
  (~/.config/lyona, ~/.local/share/lyona), install paths, the archiso
  install medium and its lyona-install/lyona-postinstall.sh scripts,
  and all documentation. The dwm window manager itself and its
  dwm-* tool family (dwm-status, dwm-settings-*, etc.) are unaffected
  -- only the project's own branding changes. No migration path is provided
  from an existing dwm-titus-named install; reinstall onto the new paths
  instead.

• Enable the multilib repository on the ISO. The archiso pacman.conf ships
  it uncommented and the generated archinstall configuration requests it, so
  the installed system has 32-bit packages available without a manual
  pacman.conf edit. install.sh now treats an already-enabled multilib as
  approval, so the ISO's full profile installs the Arch gaming packages it
  advertises instead of skipping them.

• Switch the shipped default theme from Nord to Tokyo Night and drop the
  stale include ./nord.conf line from kitty.conf, which overrode the
  generated active-theme.conf and pinned kitty to the Nord palette
  regardless of the selected theme.

• Apply a display-scale change to the running session instead of only to
  applications started afterwards. dwm-settings-display dpi-set still persists
  Xft.dpi and merges it into the running resource database, and now also
  publishes the value over XSETTINGS, sets the X server's reported DPI, and
  writes a runtime record the managed shell watches. dwm rescales its border
  width and snap distance when the resource database changes, and the Quickshell
  panel, popups, Control Center, launcher, and Settings window scale their
  metrics from the active DPI. A 96 DPI session renders exactly as before.
  Rescaling applications that are already open needs xsettingsd, which joins
  the X11 dependency set along with xorg-xrdb -- a hard requirement of the DPI
  actions that was missing from the dependency map and failed silently. Without
  xsettingsd a scale change still reaches the desktop immediately and reaches
  each application as it restarts. The scale is set from Displays in Settings.

• Keep floating windows above the tiling layout. Restacking placed every visible
  tiled client directly beneath the bar, which is the top of the window stack, so
  any floating window that was not the selected one was buried the moment focus
  moved to a tiled client. Windows that a rule, a transient hint, or a fixed size
  makes floating now stay above the tiled clients, and below the always-on-top,
  panel, override, and fullscreen layers as before. Tiled clients also restack
  correctly on a monitor that has not adopted a panel, where the previous sibling
  chain resolved to no window and the request was discarded without a diagnostic.