Full-layout Hyprlock theme not detected — host wrapper keeps `animations { enabled = false }`

[CabraLoca69]

Description

Running theme-manager hyprlock <name> on a theme that has a full Hyprlock layout
(background{}, label{}, input-field{}, image{}, etc.) still regenerates the
host ~/.config/hypr/hyprlock.conf using the old Omarchy-style wrapper, which includes
its own general{} and animations { enabled = false } blocks.

Per the README:

Full-layout Hyprlock themes use a minimal source-only host config to avoid duplicate widgets.

This is not happening — the host always ends up as:

source = ~/.config/omarchy/current/theme/hyprlock.conf
general {
    ignore_empty_input = true
}
animations {
    enabled = false
}
auth {
    fingerprint:enabled = true
}

Since the theme is source-d before the host's own conflicting blocks, the host's
animations { enabled = false } overrides any animations{} block defined inside the
theme file itself, making it impossible to enable Hyprlock animations from a theme.

Steps to reproduce

1. Create a theme at ~/.config/hypr/themes/hyprlock/<name>/hyprlock.conf with a full
   layout (background, label, input-field blocks) plus its own animations { enabled = true } block
2. Run theme-manager hyprlock <name>
3. Inspect ~/.config/hypr/hyprlock.conf — it still contains the old wrapper's
   animations { enabled = false }, which wins over the theme's setting

Expected

Host config should collapse to something like:

source = ~/.config/omarchy/current/theme/hyprlock.conf

(optionally keeping auth{} if needed), letting the theme fully control general{} and animations{}.

Environment

• theme-manager-plus version: v0.3.5
• Omarchy-based Hyprland setup