feat: theme hyprlock from the UDT palette and accent

udt-palette renders the scheme-level palette to
templates/hyprlock/hyprlock-palette.conf ($panel, $input_bg, $text,
$subtext, $fail); udt-accent writes the wallpaper accent gradient to
~/.cache/udt/hyprlock-border.conf as a hyprlang variable. The hyprlock
config sources both, so a scheme switch recolours the lock and a
wallpaper change recolours its border.

install.sh copies the palette and seeds the border from the committed
fallback on a fresh cache. Both selftests cover the new outputs.

1 files changed, 13 insertions, 0 deletions

diff --git a/install.sh b/install.sh
index 49c26c0..85d8216 100755
--- a/install.sh
+++ b/install.sh
@@ -40,6 +40,19 @@ if [ ! -f "$HOME/.cache/udt/udt-accent.rasi" ]; then
 fi
 ln -sfn "$HOME/.cache/udt/udt-accent.rasi" "$target/accent.rasi"
 
+# hyprlock. The palette is scheme-level, so it is copied like the other
+# generated configs. The border is wallpaper-level: seeded from the static
+# fallback so the lock parses before any wallpaper is processed, then rewritten
+# by udt-accent below. Both are sourced by hyprlock.conf, which carries inline
+# lavender fallbacks too, so a wiped cache degrades to lavender rather than
+# failing to lock.
+install -Dm644 "$repo/templates/hyprlock/hyprlock-palette.conf" \
+    "$HOME/.cache/udt/hyprlock-palette.conf"
+if [ ! -f "$HOME/.cache/udt/hyprlock-border.conf" ]; then
+    cp "$repo/templates/hyprlock/hyprlock-border.conf" \
+        "$HOME/.cache/udt/hyprlock-border.conf"
+fi
+
 # Firefox's bridge is the one consumer that cannot follow: pywalfox hardcodes
 # <cache>/wal/colors.json and honours only XDG_CACHE_HOME, which would move
 # every cache on the system. So udt-accent writes the real file with the rest