docs: trim never-used auto-start / service sections

The Windows-Service-on-boot and systemd `--install-service` paths are
real features in the code (WiX ServiceInstall + install.sh
install_systemd_service helper + src/service.rs), but they were never
actually exercised by the operator and the docs were prominently
promoting them as a 24/7 unattended-operation recommendation.  Better
to remove the doc paths than to keep promising a flow we haven't
validated end-to-end.

Removed from docs (CC frontend):

  - CloudNodeSetup.jsx — both "Auto-start on boot (optional)" sections
    (Windows + Linux) including the PowerShell `Start-Service /
    Set-Service SourceBoxSentryCloudNode` block, the
    `systemctl status sourcebox-sentry-cloudnode` block, and the
    `curl … | bash -s -- --install-service` example.  Trimmed the
    inline `--install-service` hint from the post-install summary.
    The "Running on Windows" + "Running on Linux/macOS" sections now
    cover the foreground-TUI path only, which matches what we
    actually use day-to-day.
  - Deployment.jsx — entire "systemd service (Linux)" section
    (heading + the full unit-file scratchpad + the enable-and-start
    example).  Also trimmed the systemd reference from the
    "Updating" paragraph.
  - Faq.jsx — Windows install FAQ entry no longer mentions the
    optional `SourceBoxSentryCloudNode` service; the rest of the
    answer (MSI download, SmartScreen warning, no PowerShell
    one-liner) is unchanged.

Kept (not touched by this commit):

  - `install.sh`'s `--install-service` flag in the script itself.
    The feature works if anyone wants it; we just stopped
    advertising it from setup docs.
  - The WiX installer's service registration in main.wxs.  Existing
    Windows installs still register a manual-start service that
    works the same way it always has — we just no longer point new
    users at it.
  - `src/service.rs` and the corresponding service-mode entry point
    in `src/main.rs`.  Dead-doc, live-code.
  - The `systemctl status` debugging hint at the top of
    `docs/runbooks/video-not-showing.md` — that's diagnostic, not
    promotional.
  - The "systemd timer" example in SecurityProcedures.jsx's
    "Cut the camera off-hours" remediation — that's suggesting
    the CUSTOMER's own scheduling mechanism, not advertising our
    service.

Refreshed backend/static/ from a clean build so the trimmed docs
ship in local-dev runs without a manual rebuild.

612 backend tests pass, frontend build clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Sbussiso

…ckend/static/assets/DocsPage-Dt0zHNYN.js …ckend/static/assets/DocsPage-D8wIfef_.jsbackend/static/assets/DocsPage-Dt0zHNYN.js renamed to backend/static/assets/DocsPage-D8wIfef_.js backend/static/assets/DocsPage-Dt0zHNYN.js renamed to backend/static/assets/DocsPage-D8wIfef_.js

@@ -24,7 +24,7 @@
     <meta name="twitter:image:alt" content="A close-up of a USB security webcam with a green LED indicator, set against a dark background with green and purple dashboard bokeh." />
 
     <title>Sentinel by SourceBox — Private Security Camera System</title>
-    <script type="module" crossorigin src="/assets/index-CkCjj4Hj.js"></script>
+    <script type="module" crossorigin src="/assets/index-DEzyi58d.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/jsx-runtime-Bg_NI1en.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-D4M6sveU.js">
     <link rel="modulepreload" crossorigin href="/assets/dist-DoOXorMg.js">

backend/static/assets/index-CkCjj4Hj.js backend/static/assets/index-DEzyi58d.jsbackend/static/assets/index-CkCjj4Hj.js renamed to backend/static/assets/index-DEzyi58d.js

@@ -52,7 +52,7 @@ function CloudNodeSetup() {
       <p style={{ marginTop: '0.75rem', fontSize: '0.9rem', color: 'var(--text-muted)' }}>
         {os === 'windows'
           ? 'After the MSI finishes, click the Sentinel CloudNode shortcut from the Start menu — first launch runs the setup wizard, every launch after streams cameras directly.'
-          : 'Run in your terminal. The script downloads the binary and registers the node. After it finishes, run the binary directly to start the foreground dashboard — same recommended path as the Windows MSI Start menu shortcut. For 24/7 unattended operation, append --install-service to register a systemd unit (opt-in).'}
+          : 'Run in your terminal. The script downloads the binary and registers the node. After it finishes, run the binary directly to start the foreground dashboard — same recommended path as the Windows MSI Start menu shortcut.'}
       </p>
 
       <h3>Setup Wizard</h3>
@@ -86,40 +86,17 @@ function CloudNodeSetup() {
           <p>
             The Start menu shortcut launches CloudNode as a foreground app — a terminal window
             opens with the live dashboard, FFmpeg starts pushing segments, and the node stays
-            online for as long as the window is open. This is the recommended path for everyday
-            use: you can see what's happening, hit a slash command, and close it cleanly.
-          </p>
-
-          <h4>Auto-start on boot (optional)</h4>
-          <p>
-            For 24/7 unattended operation, the MSI also registers a Windows Service named{' '}
-            <code>SourceBoxSentryCloudNode</code> set to <strong>manual start</strong>. Flip it
-            to automatic if you want CloudNode to come up after a reboot without anyone logging
-            in:
-          </p>
-          <div className="docs-code-block">
-            <code>{`Start-Service SourceBoxSentryCloudNode
-Set-Service -Name SourceBoxSentryCloudNode -StartupType Automatic`}</code>
-            <button className="docs-copy-btn" onClick={() => copyToClipboard("Start-Service SourceBoxSentryCloudNode\nSet-Service -Name SourceBoxSentryCloudNode -StartupType Automatic")}>Copy</button>
-          </div>
-          <p>Standard service-management commands all work:</p>
-          <ul>
-            <li><code>Get-Service SourceBoxSentryCloudNode</code> — running / stopped status</li>
-            <li><code>Stop-Service SourceBoxSentryCloudNode</code> / <code>Restart-Service SourceBoxSentryCloudNode</code></li>
-            <li><code>Get-Content -Wait C:\ProgramData\SourceBoxSentry\logs\cloudnode-service.<i>YYYY-MM-DD</i></code> — tail today's service log</li>
-          </ul>
-          <p style={{ fontSize: '0.9rem', color: 'var(--text-muted)' }}>
-            Don't run the foreground TUI and the service at the same time — only one process
-            should hold the cameras.
+            online for as long as the window is open. You can see what's happening, hit a slash
+            command, and close it cleanly.
           </p>
 
           <h3>Uninstalling</h3>
           <p>
             Use <strong>Settings → Apps → Installed apps → Sentinel CloudNode → Uninstall</strong>.
-            That stops the service (if running), removes the binary, removes the Windows Service
-            registration, and wipes <code>C:\ProgramData\SourceBoxSentry\</code> — including your
-            encrypted config and recordings. FFmpeg installed via <code>winget</code> stays put
-            because it's a separate package owned by the OS package manager.
+            That removes the binary and wipes <code>C:\ProgramData\SourceBoxSentry\</code> —
+            including your encrypted config and recordings. FFmpeg installed via{' '}
+            <code>winget</code> stays put because it's a separate package owned by the OS
+            package manager.
           </p>
           <p style={{ fontSize: '0.9rem', color: 'var(--text-muted)' }}>
             Upgrades (re-running a newer MSI) preserve everything under ProgramData; only an
@@ -145,32 +122,8 @@ Set-Service -Name SourceBoxSentryCloudNode -StartupType Automatic`}</code>
           </div>
           <p>
             A terminal dashboard opens with live cameras, segment counts, FFmpeg state, and
-            slash commands. The node stays online for as long as the window is open. This is
-            the recommended path for everyday use — same model as the Windows MSI's Start
-            menu shortcut. You can see what's happening, hit a slash command, and close it
-            cleanly with Ctrl+C.
-          </p>
-
-          <h4>Auto-start on boot (optional)</h4>
-          <p>
-            For 24/7 unattended operation (camera in a closet, no SSH session), append{' '}
-            <code>--install-service</code> to the install command. This registers a systemd
-            unit and starts it:
-          </p>
-          <div className="docs-code-block">
-            <code>curl -fsSL https://opensentry-command.fly.dev/install.sh | bash -s -- --install-service</code>
-            <button className="docs-copy-btn" onClick={() => copyToClipboard("curl -fsSL https://opensentry-command.fly.dev/install.sh | bash -s -- --install-service")}>Copy</button>
-          </div>
-          <p>Standard service-management commands all work:</p>
-          <ul>
-            <li><code>systemctl status sourcebox-sentry-cloudnode</code> — running / stopped status</li>
-            <li><code>sudo systemctl restart sourcebox-sentry-cloudnode</code></li>
-            <li><code>journalctl -u sourcebox-sentry-cloudnode -f</code> — tail live log</li>
-          </ul>
-          <p style={{ fontSize: '0.9rem', color: 'var(--text-muted)' }}>
-            Don't run the foreground TUI and the service at the same time — only one process
-            should hold the cameras. Verify the foreground flow works first before flipping
-            to unattended.
+            slash commands. The node stays online for as long as the window is open — you can
+            see what's happening, hit a slash command, and close it cleanly with Ctrl+C.
           </p>
         </>
       )}

backend/static/index.html

@@ -82,81 +82,6 @@ cargo build --release
 ./target/release/sourcebox-sentry-cloudnode setup`)}>Copy</button>
       </div>
 
-      <h3>systemd service (Linux)</h3>
-      <p>
-        The easiest path is the install script — after the wizard finishes, it offers to write
-        the systemd unit and enable it for you. If you'd rather wire it up manually, the unit
-        below mirrors what the script would have written. It assumes the binary lives at{' '}
-        <code>~/.sourcebox-sentry/sourcebox-sentry-cloudnode</code> (the install script's
-        default <code>INSTALL_DIR</code>) and the wizard wrote <code>node.db</code> under{' '}
-        <code>$HOME</code>; substitute your own paths if you installed elsewhere.
-      </p>
-      <p>Drop into <code>/etc/systemd/system/sourcebox-sentry-cloudnode.service</code>:</p>
-      <div className="docs-code-block">
-        <code>{`[Unit]
-Description=Sentinel CloudNode
-Documentation=https://opensentry-command.fly.dev
-After=network-online.target
-Wants=network-online.target
-
-[Service]
-Type=simple
-User=YOUR_USER
-# 'video' is the standard group that owns /dev/video* on Debian / Ubuntu /
-# Raspberry Pi OS — needed to open USB cameras.
-SupplementaryGroups=video
-# Inherit a sane PATH so ffmpeg (system-installed) is found even when
-# systemd's default PATH skips /usr/local/bin.
-Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-# Suppress the TUI's ANSI cursor escapes so journalctl entries stay
-# line-oriented instead of full-screen redraws.
-Environment=NO_COLOR=1
-Environment=TERM=dumb
-Environment=RUST_LOG=info
-WorkingDirectory=/home/YOUR_USER
-ExecStart=/home/YOUR_USER/.sourcebox-sentry/sourcebox-sentry-cloudnode run
-StandardOutput=journal
-StandardError=journal
-Restart=on-failure
-RestartSec=5s
-# Stop retrying after 5 failures in a minute so logs stay readable.
-StartLimitIntervalSec=60
-StartLimitBurst=5
-
-[Install]
-WantedBy=multi-user.target`}</code>
-        <button className="docs-copy-btn" onClick={() => copyToClipboard(`[Unit]
-Description=Sentinel CloudNode
-Documentation=https://opensentry-command.fly.dev
-After=network-online.target
-Wants=network-online.target
-
-[Service]
-Type=simple
-User=YOUR_USER
-SupplementaryGroups=video
-Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-Environment=NO_COLOR=1
-Environment=TERM=dumb
-Environment=RUST_LOG=info
-WorkingDirectory=/home/YOUR_USER
-ExecStart=/home/YOUR_USER/.sourcebox-sentry/sourcebox-sentry-cloudnode run
-StandardOutput=journal
-StandardError=journal
-Restart=on-failure
-RestartSec=5s
-StartLimitIntervalSec=60
-StartLimitBurst=5
-
-[Install]
-WantedBy=multi-user.target`)}>Copy</button>
-      </div>
-      <p>Enable and start:</p>
-      <div className="docs-code-block">
-        <code>sudo systemctl enable --now sourcebox-sentry-cloudnode</code>
-        <button className="docs-copy-btn" onClick={() => copyToClipboard('sudo systemctl enable --now sourcebox-sentry-cloudnode')}>Copy</button>
-      </div>
-
       <h3>Cross-compilation (Raspberry Pi)</h3>
       <p>CloudNode runs on ARM64 Linux — build on a dev machine, copy the binary:</p>
       <div className="docs-code-block">
@@ -168,10 +93,9 @@ cargo build --release --target aarch64-unknown-linux-gnu`)}>Copy</button>
 
       <h3>Updating</h3>
       <p>
-        Re-run the install script. It downloads the latest release, preserves your
+        Re-run the install script. It downloads the latest release, preserves your{' '}
         <code>data/node.db</code>, and restarts the binary. With Docker, pull the new image
-        and recreate the container. With systemd, replace the binary and run
-        <code>sudo systemctl restart sourcebox-sentry-cloudnode</code>.
+        and recreate the container.
       </p>
     </section>
   )

frontend/src/pages/docs/CloudNodeSetup.jsx

@@ -31,12 +31,10 @@ function Faq() {
           and run it. The MSI is unsigned today, so SmartScreen will warn "Windows protected
           your PC" on first run — click <strong>More info → Run anyway</strong>. After install,
           click the <strong>Sentinel CloudNode</strong> shortcut from the Start menu —
-          first launch runs the setup wizard, every launch after streams cameras directly. For
-          24/7 unattended operation, the MSI also registers an optional Windows Service named{" "}
-          <code>SourceBoxSentryCloudNode</code> that you can flip to auto-start; see the{" "}
-          <a href="#cloudnode-setup">CloudNode Setup</a> section for details. There is no
-          PowerShell one-liner installer — that path was retired in v0.1.31 because the MSI
-          is the only Windows install that handles upgrades and Add/Remove Programs cleanly.
+          first launch runs the setup wizard, every launch after streams cameras directly.
+          There is no PowerShell one-liner installer — that path was retired in v0.1.31
+          because the MSI is the only Windows install that handles upgrades and Add/Remove
+          Programs cleanly.
         </p>
       </details>