Trim comments across configs and services

Shorten verbose multi-paragraph comments to essentials, and drop a
stale claim in common.nix that jupiter kept its own copy of the base
config (it now imports common.nix directly).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

services/gitea.nix

@@ -1,22 +1,14 @@
 { ... }:
 
 # Gitea — self-hosted git. stateDir/repositories were migrated from the old
-# ZimaOS docker instance (single user/org "darman", sqlite db, 4 repos, no
-# LFS objects yet) into stateDir's default layout (data/gitea.db,
-# data/{indexers,avatars,sessions,...}, repositories/), so no import step is
-# needed on first boot — NixOS just needs to chown it to the gitea user
-# (see below).
-#
-# HTTP is reverse-proxied through Caddy (see hosts/jupiter/configuration.nix
-# for the vhost). SSH clone/push uses gitea's own built-in SSH server on
-# :2222, kept separate from the host's OpenSSH on :22. NOT :222 (the old
-# docker setup's external port) — gitea runs as the unpriv "gitea" user with
-# an empty capability set, so it can't bind <1024: "listen tcp :222: bind:
-# permission denied".
-#
-# After first deploy, fix ownership of the migrated data (it currently
-# belongs to darman:users from the CIFS copy):
+# ZimaOS docker instance straight into stateDir's default layout, so no
+# import step is needed — just chown it to the gitea user after first deploy
+# (currently darman:users from the CIFS copy):
 #   chown -R gitea:gitea /mnt/data/AppData/gitea
+#
+# HTTP is reverse-proxied through Caddy (hosts/jupiter/configuration.nix).
+# SSH uses gitea's own built-in server on :2222 (not the host's :22, and not
+# :222 — the unpriv gitea user can't bind <1024).
 {
   services.gitea = {
     enable = true;