Add multitasking controls, and a light theme for the launcher

Two things, both closing gaps in work that was already reported done.

GNOME's Multitasking panel, in Hyprland's terms: tiling layout, split
behaviour, floating-window snapping, workspace wrap-around and
back-and-forth, whether applications may take focus, and whether the
pointer changes the active display. Hyprland creates and destroys
workspaces as you use them, so there is no fixed count to expose, and
the page says so rather than leaving a conspicuous absence.

The Desktop page described the first two of these as read-only facts --
"Layout: Tiling", "Workspace movement: Dynamic" -- which was never true.
Both are ordinary Hyprland options that happened to have no controls,
and TextRow's own documentation says a setting the user could reasonably
change does not belong in it. Schema defaults are Panama's shipped
values from looks.lua rather than Hyprland's own, so restoring defaults
returns the desktop to how it ships. 43 mapped options now, from 35.

The launcher had no light theme. vicinae.json already selected a theme
per system appearance, but both entries pointed at Moon, so choosing
light mode left the most frequently opened window on the desktop dark --
a hole in the light/dark work, not a missing feature. Day is authored
from the same palette as the kitty Day theme so the two cannot drift,
and link-dotfiles now installs every authored theme rather than only the
dark one, which is why the gap survived being noticed.

Its placeholder colour is not Tokyo Night Day's own: that measures
2.54:1 against the background, below the 3:1 floor for secondary text.
This is 3.25:1, the same value used for neovim's light comments.

Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L

setup/scripts/link-dotfiles

@@ -95,19 +95,26 @@ fi
 # from ~/.config/vicinae. Keep the authored theme in Panama with the rest of
 # the launcher config and expose only that file at Vicinae's runtime path.
 VICINAE_THEME_DIR="$HOME/.local/share/vicinae/themes"
-VICINAE_THEME="$VICINAE_THEME_DIR/tokyonight-moon.toml"
 mkdir -p "$VICINAE_THEME_DIR"
 
-if [ -L "$VICINAE_THEME" ]; then
-  rm "$VICINAE_THEME"
-fi
+# Every authored theme, not just the dark one: vicinae.json selects a theme per
+# system appearance, so linking only Moon left the launcher falling back to its
+# stock palette whenever Panama was in light mode.
+for theme_src in "$PANAMA_DOT"/vicinae/themes/*.toml; do
+  [ -e "$theme_src" ] || continue
+  theme_dst="$VICINAE_THEME_DIR/$(basename "$theme_src")"
 
-if [ -e "$VICINAE_THEME" ]; then
-  log "Keeping existing Vicinae theme at $VICINAE_THEME"
-else
-  ln -s "$PANAMA_DOT/vicinae/themes/tokyonight-moon.toml" "$VICINAE_THEME"
-  log "Linked Tokyo Night Moon theme → $VICINAE_THEME"
-fi
+  if [ -L "$theme_dst" ]; then
+    rm "$theme_dst"
+  fi
+
+  if [ -e "$theme_dst" ]; then
+    log "Keeping existing Vicinae theme at $theme_dst"
+  else
+    ln -s "$theme_src" "$theme_dst"
+    log "Linked Vicinae theme → $theme_dst"
+  fi
+done
 
 # Panama-native applications live in the user data directory so launchers can
 # discover them alongside system desktop entries. Keep each authored file in