fix(motd): break getty.target ordering cycle + clean dashboard rendering

Three fixes from the latest WSL2 boot log:

1. mios-dashboard-issue.service was creating an ordering cycle:
     multi-user.target -> mios-dashboard-issue.service -> getty.target -> multi-user.target
   ...because getty.target is WantedBy=multi-user.target, and the unit
   had `After=multi-user.target` AND `Before=getty.target`. systemd
   broke the cycle by deleting getty.target's start job:
     "Job getty.target/start deleted to break ordering cycle"
   Net effect: NO console getty spawned at boot. Operators got into the
   distro via wsl.exe's /init bypass; bare-metal/Hyper-V/QEMU deploys
   would have had no login prompt.
   Removed `Before=getty.target serial-getty@.service getty@.service`
   entirely. The 2-minute OnBootSec timer + getty's Restart=always pick
   up the fresh issue.d snippet within minutes of boot anyway.

2. Dashboard double-rendered with the ASCII art bleeding into the
   MiOS module column:
       :cllllllllccclcllllllllllllcc;      MiOS
     Self-replication loopcccccccc:.
   Caused by fastfetch embedding mios-dashboard.sh --services-only as
   a custom command-module inside its side-by-side column layout, then
   the wrapper printing the services block again at the bottom.
   - Removed the MiOS custom module from fastfetch config; fastfetch
     now shows ONLY standard system info.
   - mios-dashboard.sh's default mode flow:
       header -> fastfetch (system info) -> services block -> loop hint
     Each block is full-width, no column collision.
   - Renamed print_services -> print_services_block (no loop hint
     embedded); --services-only mode prints services_block alone (used
     by /etc/issue.d/ and any future embedded contexts).

3. Loop hint no longer prints twice.

Open from this boot, NOT addressed in this commit:
   - podman-system-generator failed exit status 1 -- still happening,
     all Quadlets render as "missing" in the dashboard. Need the
     generator's stderr (`journalctl -u podman-system-generator` or
     manual invocation) to identify which .container file has bad
     syntax.
   - "Failed to connect to system scope bus" at user login despite
     dbus-daemon-wsl now showing [OK] Started -- timing or socket-path
     drift; needs a separate diagnosis pass.
   - "Credential name or glob \"tty.virtual.mios/dashboard/issue.agetty.*\"
     not valid" warnings from getty@.service:48-49 -- upstream systemd
     259 credential validator complaining about path-shaped names from
     the issue.d glob; informational only ("ignoring"), not fatal.

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

Author: Kabuki94

usr/lib/systemd/system/mios-dashboard-issue.service

@@ -12,8 +12,14 @@
 [Unit]
 Description='MiOS' dashboard -> /etc/issue.d (pre-login banner)
 Documentation=file:///usr/libexec/mios/mios-dashboard-render-issue.sh
-After=multi-user.target console-login-helper-messages.service
-Before=getty.target serial-getty@.service getty@.service
+# DO NOT use Before=getty.target -- getty.target is WantedBy=multi-user.target,
+# so combining After=multi-user.target with Before=getty.target creates an
+# ordering cycle:
+#   multi-user.target -> mios-dashboard-issue -> getty.target -> multi-user.target
+# systemd breaks the cycle by deleting getty.target's start job, which means
+# NO console getty spawns at boot. The 2-minute OnBootSec timer + getty's
+# Restart=always pick up the issue.d snippet within minutes of boot anyway.
+After=local-fs.target console-login-helper-messages.service
 ConditionPathExists=/usr/libexec/mios/mios-dashboard-render-issue.sh
 
 [Service]

usr/libexec/mios/mios-dashboard.sh

@@ -186,46 +186,41 @@ print_loop_hint() {
         "$C_GRY" "$MIOS_LINUX_USER" "$MIOS_LINUX_USER" "$C_R"
 }
 
-print_services() {
+print_services_block() {
     print_endpoints
     print_quadlets
     print_git_state
-    print_loop_hint
 }
 
 # ── Main ──────────────────────────────────────────────────────────────────────
 case "$MODE" in
     services-only)
-        print_services
+        # Used by fastfetch as a custom command-module embedded inside its
+        # column layout, AND by mios-dashboard-render-issue.sh writing to
+        # /etc/issue.d. Both contexts want the services block ALONE, no
+        # loop hint -- the wrapper that called us prints the hint itself.
+        print_services_block
         ;;
     *)
+        # Default: header -> fastfetch (system info ONLY, no MiOS module
+        # because side-by-side multi-line text bleeds into the ASCII logo
+        # column) -> services block -> loop hint.
         printf '\n  %s%sMiOS%s %sv%s%s  %s%s%s\n' \
             "$C_B" "$C_CYN" "$C_R" "$C_D" "$MIOS_VERSION" "$C_R" \
             "$C_GRY" "$(uname -srm)" "$C_R"
         hr_line 79
 
-        # Fastfetch sits between the header and the services block.
-        # Use the MiOS-themed config when present; fall back to its
-        # default when fastfetch can't find ours (e.g. fresh image
-        # before tmpfiles ran). Suppress fastfetch errors -- never
-        # block the dashboard on a fastfetch hiccup.
         if command -v fastfetch >/dev/null 2>&1; then
             local_cfg=/usr/share/mios/fastfetch/config.jsonc
             if [[ -r "$local_cfg" ]]; then
                 fastfetch -c "$local_cfg" 2>/dev/null || fastfetch 2>/dev/null || true
             else
                 fastfetch 2>/dev/null || true
             fi
-        else
-            print_services
-            exit 0
-        fi
-        # When fastfetch's custom MiOS module printed the services
-        # block, skip the second copy. Detect by checking whether the
-        # config exists -- if not, fastfetch won't have shown it.
-        if [[ ! -r /usr/share/mios/fastfetch/config.jsonc ]]; then
-            print_services
         fi
+        # Services block always renders below fastfetch (or alone if
+        # fastfetch is absent). Full-width, no column collision.
+        print_services_block
         print_loop_hint
         ;;
 esac

usr/share/mios/fastfetch/config.jsonc

@@ -1,11 +1,14 @@
 {
   "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
 
-  // MiOS fastfetch config -- standard system info + a custom MiOS module
-  // that shells out to /usr/libexec/mios/mios-dashboard.sh in
-  // --services-only mode so the self-replication-loop status (Forge / AI /
-  // Cockpit / Ollama / Quadlet rollup / git working tree state) sits
-  // inline with the other fastfetch modules.
+  // MiOS fastfetch config -- standard system info ONLY. The MiOS
+  // dashboard's services block (self-replication loop + Quadlet rollup
+  // + git state) is printed AFTER fastfetch returns, full-width, by
+  // mios-dashboard.sh's default mode. An earlier iteration embedded
+  // the services block as a fastfetch custom command-module, but
+  // fastfetch's column layout made multi-line module output bleed
+  // into the ASCII logo column on the right; rendering the block
+  // separately below fastfetch keeps both surfaces clean.
   //
   // Invoked from:
   //   /etc/profile.d/zz-mios-motd.sh  -> /usr/libexec/mios/mios-dashboard.sh -> fastfetch -c <this>
@@ -33,14 +36,6 @@
     { "type": "swap",     "key": "Swap" },
     { "type": "disk",     "key": "Disk" },
     { "type": "localip",  "key": "Local IP" },
-    { "type": "locale",   "key": "Locale" },
-    "break",
-    {
-      "type": "command",
-      "shell": "/bin/bash",
-      "key": "MiOS",
-      "keyColor": "blue",
-      "text": "/usr/libexec/mios/mios-dashboard.sh --services-only"
-    }
+    { "type": "locale",   "key": "Locale" }
   ]
 }