refactor: use flake package directly in NixOS module

Instead of requiring users to provide the package via overlay,
the module now receives `self` from the flake and uses the
package directly from `self.packages`.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

README.md

@@ -198,7 +198,7 @@ Add the module to your NixOS configuration:
 | Option | Type | Default | Description |
 |--------|------|---------|-------------|
 | `enable` | bool | `false` | Enable the listener service |
-| `package` | package | `pkgs.homelab-deploy` | Package to use |
+| `package` | package | from flake | Package to use |
 | `hostname` | string | `config.networking.hostName` | Hostname for subject templates |
 | `tier` | enum | required | `"test"` or `"prod"` |
 | `role` | string | `null` | Role for role-based targeting |

flake.nix

@@ -49,7 +49,7 @@
           };
         });
 
-      nixosModules.default = import ./nixos/module.nix;
+      nixosModules.default = import ./nixos/module.nix { inherit self; };
       nixosModules.homelab-deploy = self.nixosModules.default;
     };
 }

nixos/module.nix

@@ -1,3 +1,4 @@
+{ self }:
 { config, lib, pkgs, ... }:
 
 let
@@ -21,7 +22,11 @@ in
   options.services.homelab-deploy.listener = {
     enable = lib.mkEnableOption "homelab-deploy listener service";
 
-    package = lib.mkPackageOption pkgs "homelab-deploy" { };
+    package = lib.mkOption {
+      type = lib.types.package;
+      default = self.packages.${pkgs.system}.homelab-deploy;
+      description = "The homelab-deploy package to use";
+    };
 
     hostname = lib.mkOption {
       type = lib.types.str;