Share hypr_refresh; capture the work laptop's own units

Both laptops run hypr_refresh and their unit files had diverged. The work
laptop's is the refined one — Type=oneshot, which is correct for a script
that exits, a 15s interval with AccuracySec, and a comment explaining the
wallpaper-daemon guard. system76 had Type=simple with Restart=on-failure,
which respawns a oneshot script continuously. Shared version wins.

Three more units existed only on the work laptop and were untracked:
backlight-probe, kanshi and mopidy.

hosts/sctfw004/systemd/backlight-probe.service

@@ -0,0 +1,9 @@
+[Unit]
+Description=Sample backlight state to diagnose failed restores
+
+[Service]
+ExecStart=%h/.dotfiles/hosts/sctfw004/bin/backlight-probe
+Restart=always
+
+[Install]
+WantedBy=default.target

hosts/sctfw004/systemd/kanshi.service

@@ -0,0 +1,21 @@
+[Unit]
+Description=kanshi dynamic output configuration
+PartOf=graphical-session.target
+StartLimitIntervalSec=60
+StartLimitBurst=5
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/kanshi
+Restart=always
+RestartSec=1
+
+# kanshi 1.5.1 can wedge into a tight profile-list loop that forks a shell per
+# iteration. These bound the blast radius rather than prevent it.
+CPUQuota=20%
+LogRateLimitIntervalSec=10s
+LogRateLimitBurst=200
+TasksMax=64
+
+[Install]
+WantedBy=graphical-session.target

hosts/sctfw004/systemd/mopidy.service

@@ -0,0 +1,10 @@
+[Unit]
+Description=Mopidy music server
+After=network.target sound.target
+
+[Service]
+ExecStart=/usr/bin/mopidy --config /etc/mopidy/mopidy.conf
+Restart=on-failure
+
+[Install]
+WantedBy=default.target