feat: opt-in Windows service mode (boot-time, one elevation) + v1.0.0

The per-user Startup-folder launcher (W3) only ever runs after this user
signs in. A real Windows Service would start earlier, but under
LocalSystem/NetworkService -- accounts with no normal profile, so
%LOCALAPPDATA%\meshbay\ (config, keystore, data) would not exist for it.
Relocating storage to make that work is real surgery, deliberately not
done here.

Instead: a Scheduled Task, created once with admin rights, that runs AS
THIS USER at boot without needing them to sign in first.
`schtasks /create ... /ru <user> /rp ""` with no `/it` registers an S4U
(Service For User) logon -- no password stored anywhere, and unlike
LocalSystem it loads this account's own profile, so config_dir()/
data_dir() need zero changes. The cost: S4U carries no network credential,
which the node never needed -- everything it touches is local disk plus
outbound internet. Creating the task needs admin (a boot trigger touches
system-wide scheduler state, the same reason /sc onlogon needed it);
querying/starting/stopping an existing one does not -- Task Scheduler
grants the owning user that much itself, which is what lets the Node
page's Start/Stop/Restart drive it with no further UAC prompts.

meshbay_node/platform.py
  service_install/_remove/_status/_run/_end -- mirrors autostart_* but
  for the Scheduled Task; TASK_NAME moved here (was decorative before)

meshbay_node/daemon.py
  new `service install|remove|start|stop|status` verb; restart-daemon and
  reset now check for the service task too

packaging/win/service.ps1
  the installer-side equivalent (extraResource); status/run/end never
  self-elevate -- only install/remove do, exactly matching what
  Task Scheduler itself requires

packaging/win/service-mode.ps1
  ONE elevated helper running service.ps1 + firewall.ps1 together, so
  choosing service mode costs exactly one UAC prompt, not two

build/installer.nsh
  the install-time choice: "run as a background service?" (one
  elevation, both jobs) vs the existing per-user + separate firewall
  question. Checked first, unelevated, so re-running setup with
  everything already configured asks nothing. Uninstall offers the
  matching one-elevation cleanup, default No.

src/main.js
  winServiceTaskStatus/Run/End, wired into node:installed,
  node:service-status/-stop/-restart and node:start: when the Scheduled
  Task exists, drive it; otherwise fall back to the existing per-user
  spawn/kill path. This is the hard requirement -- Start/Stop/Restart
  from the Node page must work in either mode.

node-page.js / locales
  a hint explaining why the per-user autostart toggle is absent when
  service mode is active (info.mode from the backend, no new field to
  gate on -- it just isn't sent in that case)

package.json: 0.1.0 -> 1.0.0.

Verified: electron-builder compiles the new NSIS choice logic and ships
all three scripts; service.ps1's S4U install fails cleanly (Access
denied) when run unelevated, and its status/run/end never touch "runas".
Cannot verify the elevated success path myself (no admin in this
session) -- that needs a real UAC click. Node suite 843 pass / 25 skip;
test_packaging_win.py pins the one-elevation property, the S4U flags,
and that main.js actually checks the service task in all three handlers.

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

1 files changed, 55 insertions, 0 deletions

diff --git a/packaging/win/service-mode.ps1 b/packaging/win/service-mode.ps1
new file mode 100644
index 0000000..e522f04
--- /dev/null
+++ b/packaging/win/service-mode.ps1
@@ -0,0 +1,55 @@
+<#
+.SYNOPSIS
+    Elevated helper: set up (or tear down) service mode in ONE UAC prompt,
+    not two.
+
+.DESCRIPTION
+    "Run as a background service" is two things -- the boot-time Scheduled
+    Task and the firewall rules -- and needs one elevation, not one each.
+    build/installer.nsh runs this single script via ExecShellWait "runas"
+    for both the install-time choice and the uninstaller's cleanup, instead
+    of elevating service.ps1 and firewall.ps1 separately.
+
+    Each stays a script of its own rather than being folded together, so both
+    remain independently callable and testable -- the CLI does, through
+    meshbay-node service, and so does a later "just fix the firewall rules"
+    retry that has nothing to do with the service task.
+
+    Logs to the same file firewall.ps1 already uses, so both are visible in
+    one place: %TEMP%\meshbay-firewall.log.
+
+.PARAMETER Action
+    install  service.ps1 install, then firewall.ps1 add
+    remove   service.ps1 remove,  then firewall.ps1 remove
+#>
+[CmdletBinding()]
+param(
+    [ValidateSet("install", "remove")]
+    [string]$Action = "install"
+)
+
+$here = $PSScriptRoot
+$log = Join-Path $env:TEMP "meshbay-firewall.log"
+$firewallAction = if ($Action -eq "install") { "add" } else { "remove" }
+$failed = $false
+
+"[{0}] service-mode {1}" -f (Get-Date -Format s), $Action | Add-Content $log
+
+try {
+    & (Join-Path $here "service.ps1") $Action
+}
+catch {
+    "  service $Action failed: $_" | Add-Content $log
+    $failed = $true
+}
+
+try {
+    & (Join-Path $here "firewall.ps1") $firewallAction
+}
+catch {
+    "  firewall $firewallAction failed: $_" | Add-Content $log
+    $failed = $true
+}
+
+if ($failed) { exit 1 }
+exit 0