sync: auto-sync from GURU-5070 at 2026-06-11 08:01:12

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-11 08:01:12

.claude/memory/gururmm-physical-server-storage.md

@@ -25,9 +25,16 @@ direct (id-range filtered, .pgpass), 3.46M rows / ~3.4 GB in ~2.5 min, lossless
 match VM<->new box: metrics 1,189,924; agent_logs 2,262,938). **Perf proof:** SSD sustained
 186-214 MB/s writes, w_await 0.7-3.2 ms, fsync ~3 ms, peak %util ~65% (headroom), and ZERO
 pool-timeouts under the bulk load + 212 live agents -- the rotational-VM WAL-fsync root cause is fixed.
-**Still pending post-cutover:** Gitea runner -> Jupiter Docker (Workstream B); drop `.47` (new box)
-+ `.46` (VM) mgmt IPs; decommission the old VM after a stability soak (VM is parked on .46, powered
-on, DATA PRISTINE for rollback -- do NOT delete yet).
+**Workstream B DONE (2026-06-11):** jupiter-runner (act_runner v0.6.1, labels ubuntu-latest/22.04)
+online on Jupiter .20 Docker; VM's gitea-runner DISABLED (kept registered for rollback). Build env
+provisioned on the new box: source repo /home/guru/gururmm @ main 7c2f20e (rsync'd from VM, target/
++node_modules excluded), last-built-commit baselines copied, Rust 1.96.0 + Node v20.20.2/npm 10.8.2,
+Pluto (Administrator@172.16.3.36) SSH auth OK for Windows builds. NOTE: gururmm has NO .gitea/workflows
+-- builds run via the **webhook-handler path** (Gitea webhook http://172.16.3.30/webhook/build ->
+nginx :80 /webhook/ -> :9000 -> build-*.sh on the server), NOT Gitea Actions. Pipeline wired end-to-end;
+not yet exercised by a real build. **Still pending post-cutover:** drop `.47` (new box) + `.46` (VM)
+mgmt IPs; decommission the old VM after a stability soak (VM parked on .46, powered on, DATA PRISTINE
+for rollback -- do NOT delete yet).
 
 
 The GuruRMM server/build-pipeline is being migrated from the VM (172.16.3.30, slow