catppuccin/nix alongside stylix: helix theme conflict and stylix's non-color roles

Adding catppuccin/nix (catppuccin.enable = true; flavor = "macchiato") to a NixOS+home-manager flake that already uses stylix: catppuccin.enable auto-enables every port (autoEnable defaults to catppuccin.enable), so any app where you set the theme yourself clashes at eval. First hit: programs.helix.settings.theme has conflicting definition values (user's custom theme vs catppuccin's "catppuccin-macchiato"). Fix by deleting the custom theme, or with catppuccin.helix.enable = false / lib.mkForce.

Home-manager wiring: import inputs.catppuccin.nixosModules.catppuccin and add inputs.catppuccin.homeModules.catppuccin to home-manager.sharedModules. homeManagerModules is deprecated and renamed to homeModules.

Deciding whether to drop stylix: catppuccin/nix only handles colors. Stylix also installs fonts, sets fontconfig defaults and per-app fonts, the cursor and terminal opacity, and exposes config.lib.stylix.colors and config.stylix.fonts that other modules may read. A low-effort middle ground is to keep stylix with base16Scheme = "${pkgs.base16-schemes}/share/themes/catppuccin-macchiato.yaml", so apps catppuccin doesn't port still match. Stylix has no global colors-off switch; color toggles are per target (stylix.targets.<name>.colors.enable).

Discord: catppuccin/nix ports vesktop, not discord+Vencord, so stylix's vencord target is the only automatic option for the latter.