SDDM greeter's Hyprland config ignores system keyboard layout, causing password mismatches for non-US layouts

[winless-code]

Title: SDDM greeter's Hyprland config ignores system keyboard layout, causing password mismatches for non-US layouts

What happened

The SDDM Wayland greeter runs its own minimal Hyprland instance via
/usr/share/sddm/hyprland.lua (referenced from
/etc/sddm.conf.d/10-wayland.conf as CompositorCommand). This config has
no input block, so it falls back to Hyprland's default keyboard layout
(US), regardless of the system's actually configured layout
(localectl correctly reports de for both console and X11).

This is invisible for most passwords, but any password containing a
character that sits on a different key between the US and configured
layout (e.g. _ on a US vs. German keyboard) gets typed incorrectly at
the greeter — while working fine on a TTY or inside the real Hyprland
session, since those correctly use the system layout.

What was expected

The SDDM greeter should use the system's configured keyboard layout
(as reported by localectl status), matching what the TTY and the
user's actual Hyprland session use — so password entry is consistent
across all three.

Steps to reproduce

1. Install Omarchy on a system with a non-US keyboard layout (e.g. de)
   configured via localectl / /etc/vconsole.conf.
2. Set a password containing a character that differs in position between
   the US and configured layout (e.g. _, which is Shift+Minus on US but
   a different key combination on German layout).
3. Reboot to the SDDM login screen and enter the password.
4. Login fails — the greeter's default US-layout Hyprland instance
   produces the wrong character(s). Password verified independently
   (e.g. via openssl passwd -6 against /etc/shadow) confirms it's
   correct; entering the same password on a TTY works.

Workaround

Manually add an input block to /usr/share/sddm/hyprland.lua:

hl.config({
  input = { kb_layout = 'de' },
  ...
})

This is not durable: the file is owned by the omarchy-settings package
and has no pacman backup/pacnew protection, so it is silently overwritten
(and the bug reintroduced) on the next omarchy update.

System details

• Omarchy version: 4.0.2-1
• Kernel: 7.1.9-arch1-2
• CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
• GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] (i915 driver)
• Keyboard layout: de (confirmed via localectl status: VC Keymap, X11 Layout both de)