feat(install): track rofi scripts, wire nvim and hypr-theme, merge qt/gtk keys

The rofi menus' launch scripts lived loose in ~/bin, so the themes were
tracked and the only things that open them were not. They now live in bin/
and are symlinked under the names hypr-theme's keybindings call.

neovim gets a generated colorscheme: catppuccin/nvim with all 26 palette
colours overridden from the active scheme, selected by rewriting only the
colorscheme line of init.vim. hypr-theme is linked as the whole of
~/.config/hypr, leaving a real directory there alone.

The qt-gtk templates were reference copies nothing installed. They now hold
theme keys only and ini_merge writes them into the live qt5ct, qt6ct and
gtk3 files key by key, keeping every other line; tests/ini-merge.sh checks
it. The stale kvantum.kvconfig template is gone, install.sh writes that file.

Fresh-machine fixes: settings.ini and ~/.config/gtk-4.0 are created when
missing instead of aborting under set -e, and conky is found as a sibling
checkout and skipped when absent, in udt-palette as well as install.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 24 insertions, 1 deletions

diff --git a/AGENTS.md b/AGENTS.md
index 67e3440..3acdc98 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -14,6 +14,27 @@ the working config cannot drift from what is committed. Everything outside
 `~/.config/rofi/udt/` and `~/bin/` was edited in place; `docs/MIGRATION.md` is
 the record of what changed and where the backups are.
 
+The rofi menus' launch scripts (`udt-powermenu.sh`, `udt-launcher.sh`,
+`qar-scrotmenu.sh`) live in `bin/` and are symlinked into `~/bin/` under the
+names hypr-theme's keybindings call. They used to sit loose in `~/bin/`, so the
+themes were tracked and the only things that open them were not.
+
+Sibling checkouts are wired from here, each skipped when not cloned:
+`waybar-theme-udt` (its own `install.sh`), `conky-theme-udt` (five links into
+`~/.config/conky/`) and `hypr-theme`, which is the whole of `~/.config/hypr` as
+one symlink. A real `~/.config/hypr` directory is left alone with a warning.
+
+Live files that mix theme keys with anything else are merged, never replaced:
+`install.sh`'s `ini_merge` writes every key in `templates/qt-gtk/qt5ct.conf`,
+`qt6ct.conf` and `gtk3-settings.ini` into the live file and keeps every other
+line. So those templates hold theme keys only; icons and cursor are the
+appearance drawer's. `tests/ini-merge.sh` checks the merge.
+
+neovim runs `colorscheme udt`, a generated `templates/nvim/udt.lua` linked into
+`~/.config/nvim/colors/`. It is catppuccin/nvim with all 26 palette colours
+overridden, so every highlight group follows the scheme without restating one.
+`install.sh` rewrites only the `colorscheme` line of `init.vim`.
+
 ## One palette, many consumers
 
 Colours are written down once. `palette/<scheme>.conf` holds them under the
@@ -45,7 +66,8 @@ The generated set is `rofi/udt/palette.rasi`,
 `templates/sublime/udt.sublime-color-scheme`,
 `templates/sublime/udt.sublime-theme`, `templates/gtk/gtk{3,4}.css`,
 `templates/gtk/index.theme`, `templates/gtk/assets/*.svg`,
-`templates/hyprlock/hyprlock-palette.conf` and `bin/udt_colors.py`.
+`templates/hyprlock/hyprlock-palette.conf`, `templates/nvim/udt.lua` and
+`bin/udt_colors.py`.
 
 Sublime is two outputs, not one. The **colour scheme** is the editor pane and
 tracks the wallpaper accent. The **theme** is the UI chrome, and is an override
@@ -280,4 +302,5 @@ The table is what it does, and what to run if you change a config by hand.
 | kitty | `pkill -USR1 -x kitty` |
 | Sublime Text | nothing; it watches `Packages/User` and reloads both the scheme and the theme |
 | conky | restart it; no hot-reload |
+| neovim | `:colorscheme udt`, or restart it |
 | Qt / GTK apps | restart the app |