style: scope in-file comments to the current file state

In-file comments should describe only what the file currently is, not task
numbers, external tooling, or past/future states.

- hosts/neogaia: drop the "replaced by disko" / "arrive later" framing;
  describe the filesystems and hardware profile as the placeholder values
  they are.
- lib: drop the "no null-placeholder traversal hack" comparison to a prior
  implementation.
- system: drop "no impure environment lookup" from the user.name description
  and the sops/post-boot roadmap from the user comment.

system/default.nix

@@ -23,10 +23,8 @@ in
       type = types.str;
       default = "alexion";
       description = ''
-        The primary interactive user this Host is built for. An explicit option
-        with no impure environment lookup, so the config is reproducible and
-        honest about who the user is. Drives both the system account and the
-        home-manager user in lockstep.
+        The primary interactive user this Host is built for. Drives both the
+        system account and the home-manager user in lockstep.
       '';
     };
     description = mkOption {
@@ -55,9 +53,7 @@ in
     ];
     environment.systemPackages = [ pkgs.git ];
 
-    # Primary user, in wheel. The bootstrap password is set by hand at install
-    # time and never committed; moving it to a sops-backed hashedPasswordFile is
-    # the first post-boot task (out of scope for the MVI).
+    # Primary user, in wheel. No password is set here.
     users.users.${user.name} = {
       isNormalUser = true;
       description = user.description;