## gui package — put HyDE's script dir on the *session* PATH: the compositor and
## everything it spawns directly (raw exec binds, terminals) resolve bare hyde
## script names through it. Nothing else adds it — HyDE only self-bootstraps PATH
## inside its own wrappers (hyde-shell/app.sh), so a bare script name execed
## outside that lineage is "command not found" (TROUBLESHOOTING.md symptom 8).
## The systemd-unit side is covered by the twin
## gui/.config/environment.d/10-hyde-path.conf — both are needed.
## No ordering constraint vs hyde.fish (it never touches this dir).
fish_add_path --global ~/.local/lib/hyde