Remove top-level gtk-sni-tray, gtk-strut, status-notifier-item,
dbus-menu, and dbus-hslogger inputs that only existed as follows
targets. Let taffybar and imalison-taffybar resolve their own
ecosystem deps, eliminating cascading lock update headaches.
Also rename bitwarden -> bitwarden-desktop in kat.nix (nixpkgs rename).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Without --all, only dangling (untagged) images were pruned,
allowing tagged-but-unused CI images to accumulate (~223G).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add hyprscratch from colonelpanic8/reapply-rules-on-toggle fork that
reapplies size/position/float rules on every toggle (not just spawn)
- Configure 9 scratchpads: htop, volume, spotify, element, slack,
transmission, dropdown, gmail, messages
- Use clean mode (hide on workspace change) and auto-dismiss (only
dropdown persists)
- Fix pavucontrol class (org.pulseaudio.pavucontrol) and dropdown
position (offset by taffybar height)
- Add kanshi-sni, dbus-menu, dbus-hslogger flake inputs and follows
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Separate the taffybar ecosystem release workflow (Hackage publishing,
dependency graph, version bounds) from the NixOS flake chain integration
(three-layer flake.lock cascade, bottom-up update strategy). Each skill
cross-references the other.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Move enable propagation into the modules themselves instead of
desktop.nix. Relax the assertion to only prevent both taffybar
and waybar from being enabled simultaneously.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Hackage can't build docs for packages with GTK/GI system deps. This
affects taffybar, gtk-sni-tray, gtk-strut, and dbus-menu — docs must
be built locally and uploaded manually for those.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Split the skill into two clear concerns: the taffybar org package
release workflow (dependency graph, Hackage publishing, version bounds)
and the personal NixOS flake chain integration. The NixOS section
explains the three-layer flake.lock cascade and why bottom-up updates
matter, without being prescriptive about always doing all layers.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
