Ship OpenClaw itself again until a release can seed it (#796)

This reverts f6b9267b (#651), at pkgrel 3 so it replaces 2026.9.6-2. OpenClaw rides the fast ring, so the seed package went straight to edge, rc and stable, where omarchy is still 4.0.4: nothing there seeds ~/.openclaw or moves an existing install, so every OpenClaw user lost the openclaw command on their next update while 4.0.4's --check went on calling it installed. The seed comes back with the Omarchy release that carries omacom/omarchy#13296.

pkgbuilds/openclaw/openclaw.install

@@ -1,17 +1,17 @@
 post_install() {
     printf "%s\n" \
-        "==> This is the release a self-updating OpenClaw starts from." \
-        "==> Set it up under ~/.openclaw: omarchy-install-openclaw-cli --now"
+        "==> Install gateway service: openclaw gateway install --force" \
+        "==> Perform onboarding once: openclaw onboard"
 }
 
 post_upgrade() {
-    # Earlier releases of this package were OpenClaw itself, under
-    # /usr/lib/node_modules/openclaw, and which of those a machine is leaving
-    # cannot be told from the version alone, since the upstream sync moves it.
-    # A root pacman hook has no session bus to move a user's OpenClaw, so
-    # Omarchy's migration does, and this says what happens either way.
+    # The gateway runs as a systemd user unit (openclaw-gateway.service in
+    # ~/.config/systemd/user), which a root pacman hook has no session bus
+    # to reach, so it cannot be restarted from here and keeps running the
+    # old code until the user restarts it.
     printf "%s\n" \
-        "==> OpenClaw runs from ~/.openclaw and updates itself: openclaw update" \
-        "==> This package only sets the release new installs start from;" \
-        "    omarchy update moves an OpenClaw still running from /usr there."
+        "==> Restart the gateway to apply updates:" \
+        "    openclaw gateway restart" \
+        "==> Run doctor to migrate configs, check gateway health, etc.:" \
+        "    openclaw doctor"
 }