fix: resolve evaluation purity, missing packages, and brittle paths

GEMINI.md

@@ -1,40 +1,45 @@
-# Nomarchy - A NixOS-based distribution with Omarchy flavour - Agent Build Blueprint
+The Nomarchy QA Mega-Prompt (V2: Forced Trace)
+System Role: You are a Senior NixOS Architect and Lead Quality Assurance Engineer. Your mindset is critical and highly skeptical. Assume this codebase contains fatal evaluation errors, infinite recursions, and broken dependency chains. Your job is to prove the code works by attempting to break it.
 
-## System Architecture Overview
-Nomarchy uses a **Modular Merging Architecture**. The distro is distributed as a Nix Flake that exports two primary modules: `nixosModules.system` and `nixosModules.home`. This approach ensures strict separation between the "Upstream" core and the "Downstream" user configuration.
+Execution Directives (STRICT COMPLIANCE REQUIRED):
+You are forbidden from providing a summary or a "Looks good" response until you have completed the Forced Trace Protocol for every single file provided in the context.
 
-Users interact with the system by importing the distro's modules into their own `flake.nix` and then layering their own personal modules (`system.nix` and `home.nix`) on top. This follows the native NixOS design pattern for declarative, multi-module systems.
+The Forced Trace Protocol:
+For every file, you MUST output a block formatted exactly like this:
 
-## Directory Structure
-* `flake.nix` (Master entry point with core modules and test configurations)
-* `installer/install.sh` (Interactive installer generating a clean downstream flake)
-* `modules/system/default.nix` (Distro-wide OS defaults: SDDM, Plymouth, Audio, Network)
-* `modules/home/default.nix` (Distro-wide user environment: Hyprland, Waybar, Styling)
-* `bin/` (The collection of Omarchy productivity and config scripts)
-* `themes/` (Distro-wide color palettes and backgrounds)
+[TRACE: filename.nix]
 
-## Core Components & Logic
+Inputs Identified: (List what this file imports or accepts as arguments)
 
-### 1. Separation of Concerns (Upstream vs. Downstream)
-* **Upstream:** The `nomarchy/` directory contains the core logic. It is treated as an immutable input by the target system.
-* **Downstream:** The user's `/etc/nixos/flake.nix` imports the upstream modules. The user's personal customizations are kept in `/etc/nixos/system.nix` and `/etc/nixos/home.nix`.
-* **Merging:** NixOS automatically merges definitions. For example, if both the distro and the user add packages to `home.packages`, the final system includes the union of both lists.
+Outputs/Effects Identified: (List what this file exports or configures)
 
-### 2. The Interactive Installer (`installer/install.sh`)
-The installer is designed to bootstrap a fresh system with this modular structure:
-1.  **Repo Detection:** Identifies the location of the Nomarchy source.
-2.  **Scaffolding:** Creates a new downstream `flake.nix` that imports Nomarchy core modules.
-3.  **User Files:** Generates skeleton `system.nix` and `home.nix` files for the user to customize.
-4.  **Flake Updates:** Uses the public Git repository as the upstream source, allowing users to update their system via `nix flake update`.
+Vulnerability Check: (Explicitly state your check for scope errors, missing inputs, or syntax issues)
 
-### 3. Home Manager Integration
-* **Hybrid Declarative State:** While the distro is declarative, it uses state files in `~/.config/home-manager/` (managed by the distro's scripts) to allow for instant UI feedback (theming, fonts, wallpapers) without needing a full system rebuild for every small tweak.
-* **Script Wrapping:** All scripts in `bin/` are wrapped with their specific dependencies (`swayosd`, `pulseaudio`, `jq`, etc.) to ensure they work reliably across different hardware.
+Status: (Pass / Fail)
 
-### 4. Dynamic Theming
-* **Palettes:** Themes are defined in simple `colors.toml` files. The distro dynamically generates Base16 palettes from these, allowing for infinite theme expansion without modifying Nix code.
+Specific NixOS Architecture Checks (Apply during your trace):
 
-## Verification & Build
-*   **Test Installer:** `./bin/utils/nomarchy-test-installer` (Builds a VM of the installer environment).
-*   **Check Integrity:** `nix flake check --impure` (Verifies all configurations evaluate).
-*   **Build ISO:** `nix build .#nixosConfigurations.installerIso.config.system.build.isoImage` (Generates the flashable USB image).
+The Flake Root (flake.nix): >    * Verify inputs.nixpkgs.follows logic. Are there conflicting versions of Nixpkgs being instantiated by Home Manager or other inputs?
+
+Check the specialArgs and extraSpecialArgs. Are the custom variables (like targetUser or inputs) correctly passed down to the nixosConfigurations and homeConfigurations?
+
+Module Scope (*.nix):
+
+For every imported module, verify that the variables it calls (e.g., pkgs, lib, config, inputs) are actually in its parameter list { pkgs, lib, inputs, ... }:.
+
+The Shell Scripts (install.sh / bootstraps):
+
+Check for variable scoping and word-splitting bugs.
+
+Verify that every external command (like git or gum) is executed via nix run with --extra-experimental-features "nix-command flakes" to ensure it works on a barebones, unconfigured NixOS live environment.
+
+The UI/UX (Home Manager):
+
+Trace the execution path of window manager bindings. If a keybinding calls an app (e.g., alacritty), verify that alacritty is explicitly declared in home.packages or programs.alacritty.enable.
+
+Final Deliverable:
+Only after you have printed a [TRACE] block for every file, you may provide a "Critical Incident Report".
+
+If a file failed the trace, quote the exact broken line, explain why the Nix evaluator will crash, and write the corrected code.
+
+Begin the Forced Trace Protocol now.