CI and devshell comments say what the config does: jobTimeout bounds jobs, coverage runs nightly, dead timeout keys removed

Job-level timeout-minutes is parsed but not enforced by this runner; only
the runner's jobTimeout bounds a job. Also fixes the devshell coverage
comment, the shellcheck job comment, an option description citing a script
that is not in the repo, and comment file pointers that resolve to nothing.

nix/devshell.nix

@@ -1,6 +1,6 @@
 # Dev shell: the rust toolchain plus the exact native build inputs
 # the crane derivations use (git, sqlite, pkg-config, cmake — see
-# ../rust.nix), so a plain `cargo build` / `cargo test` in the shell
+# ./rust.nix), so a plain `cargo build` / `cargo test` in the shell
 # sees the same toolchain shape as CI.
 { pkgs, rust }:
 {
@@ -46,8 +46,8 @@
     #
     # Coverage is deliberately NOT part of `nix flake check`: an
     # instrumented build cannot reuse the normal test artifacts, so it
-    # roughly doubles a test job. It runs on manual dispatch — see
-    # .forgejo/workflows/coverage.yml for why that rather than nightly.
+    # roughly doubles a test job. It runs nightly and on manual dispatch — see
+    # .forgejo/workflows/coverage.yml.
     LLVM_PROFDATA = "${pkgs.llvmPackages.llvm}/bin/llvm-profdata";
     LLVM_COV = "${pkgs.llvmPackages.llvm}/bin/llvm-cov";
   };

nix/host-modules/hive-forge/default.nix

@@ -143,8 +143,8 @@ in
   # view: the names and ports it answers on, the URLs it advertises, and the
   # client id it is registered under. What lives here is what the host running
   # it decides — which build it runs, how it is served, what it mirrors, and
-  # where its host-local secrets sit. Same rule as ./swarm-victorialogs.nix,
-  # and the renames are in ./deploy.nix with the rest.
+  # where its host-local secrets sit. Same rule as ../swarm-victorialogs.nix,
+  # and the renames are in ../deploy.nix with the rest.
   options.services.hyperhive.deploy.forgejo = {
     package = lib.mkOption {
       type = lib.types.package;

nix/host-modules/hive-tls.nix

@@ -40,7 +40,7 @@ let
   # reach the store, and waiting on a login to that store would take that
   # path down whenever it is sealed. There the gateway starts on the hive
   # leaf, or on a host without a hive on a throwaway self-signed pair
-  # (../hive-gateway/default.nix), and the issuing script re-imports the
+  # (./hive-gateway/default.nix), and the issuing script re-imports the
   # services leaf into the running nginx once it lands.
   #
   # Nor on a host fronting no swarm name: it asks the store for the root
@@ -51,7 +51,7 @@ let
 
   # The hive leaf, `hive-tls-resign` and the hive identity it needs exist only
   # where a hive runs. A gateway host without one serves the swarm-services
-  # leaf in their place (../hive-gateway/default.nix).
+  # leaf in their place (./hive-gateway/default.nix).
   runsHive = hyperhiveCfg.deploy.hive-controller.enable;
 
   # The gateway's own leaf is only issued when the gateway actually serves a

nix/host-modules/swarm-victorialogs-service.nix

@@ -57,8 +57,8 @@ in
         ⚠️ Every swarm container shares the host's network namespace, so
         this is a swarm-wide claim rather than a per-container one — two
         modules picking the same number collide at runtime with no bind
-        error and nothing in any log. `state/eval-port-collisions.sh`
-        checks the class.
+        error and nothing in any log. No repo-wide
+        check catches it.
       '';
     };