fix(deploy): drop stale content-editor systemd restart from staging script

scripts/deploy_to_stage_on_local.sh restarted a
"mozdit-content-editor.service" systemd unit after every staging deploy
— the old custom CMS's own service (content-editor.js, retired in
MITHOME-93). Left in place, the next staging deploy would pull the
commit that deletes content-editor.js and then try to restart a
service pointing at a now-missing script.

Removed the restart from the deploy script; the server-side systemd
unit itself (if still installed) needs a manual stop/disable — out of
reach from here (no SSH access in this session), flagging it to the
user instead.

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

scripts/deploy_to_stage_on_local.sh

@@ -45,8 +45,14 @@ printf '2/4 Commit feltolása a Gitea-ra…\n'
 git push origin "${DEPLOY_BRANCH}"
 
 printf '3/4 Staging deploy (%s:%s)…\n' "${STAGE_HOST}" "${STAGE_PATH}"
+# WHY nincs itt már "sudo systemctl restart mozdit-content-editor.service": az a
+# régi egyedi CMS (content-editor.js) külön systemd szolgáltatása volt — a
+# fájlt MITHOME-93 leépítette, a Docker-compose alapú app (deploy.sh) a
+# régóta egyedüli kiszolgáló. A szerveren futó mozdit-content-editor.service
+# unit-ot (ha még létezik) manuálisan kell leállítani/letiltani — ezt a
+# scriptet nem futtatjuk SSH-n keresztül automatikusan.
 ssh -o BatchMode=yes -o ConnectTimeout=15 "${STAGE_HOST}" \
-  "cd '${STAGE_PATH}' && git pull --ff-only origin '${DEPLOY_BRANCH}' && ./deploy.sh staging && sudo systemctl restart mozdit-content-editor.service"
+  "cd '${STAGE_PATH}' && git pull --ff-only origin '${DEPLOY_BRANCH}' && ./deploy.sh staging"
 
 printf '4/4 Staging smoke teszt (%s)…\n' "${STAGE_URL}"
 (