Skip to content

armgit / mso

Public Imported from GitHub
0

Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.

fix(release): reconcile locked installer with portable proxy

Rahmane0b9cc6542fd
diff --cc docs/CHANGELOG.md
index cc6aa747,b113cacc..1cfb3aad
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@@ -13,7 -13,7 +13,8 @@@ this is the *what*, and it is what Sett
**Fixed**
+ - `installer` lock isolated native build tool dependencies
+- `proxy` finish portable managed-app loopback relay
- `workflows` pin private storage reads and atomic writes
- `ci` preserve strict scanner coverage on hosted release
- `forge` make sandbox bootstrap portable on hosted Linux
diff --cc docs/PROGRESS.md
index fa0cf9af,4266e7af..5b152582
--- a/docs/PROGRESS.md
+++ b/docs/PROGRESS.md
@@@ -1,18 -1,15 +1,30 @@@
+ ## 2026-09-17 — Lock the native build bootstrap without touching the runtime tree
+
+ The complete PR/branch audit found open Scorecard finding #136 in the user-local
+ `node-gyp` bootstrap. An exact top-level version still allowed fresh transitive
+ resolution. The helper now installs from a committed npm lock containing integrity
+ hashes for all resolved packages, with lifecycle scripts disabled. A manifest-hash
+ cache and private atomic staging preserve existing user-selected cache roots and
+ never run `npm ci` against the MSO checkout. Cache validation, failed-install cleanup,
+ wrong-version and symlink refusal, native-binding checks and the installer's outer
+ recovery trap are covered. Node, node-gyp's existing version, Bun, privileges, bind
+ addresses and runtime behavior are unchanged; no scanner suppression was added.
+
+## 2026-09-17 — Finish the verified branch release and loopback managed-app relay
+
+The release audit reconciled the dormant Workflow/Organization controls, exact artifact history,
+private-store hardening and bundle work through PR #47 rather than rewriting their source branches.
+All candidate changes were already gated; this handoff independently rechecked 83 targeted tests,
+typecheck and current PR checks before integration. Dirty worktrees, stashes, historical alternatives
+and recovery refs remain preserved; an old branch name alone is not evidence of a missing feature.
+
+The remaining managed-app relay patch was reproduced with a failing reverse-proxy test, then applied
+from the preserved source after reviewing its two-file delta. Public HTTPS headers can describe an
+HTTP loopback Next listener as HTTPS; internal managed-app rewrites now correct only loopback
+transport while retaining the public scheme for non-loopback origins. Regression cases cover
+localhost, IPv4 and IPv6 loopback, query preservation and unchanged public-host/cross-origin guards.
+There is no bind-address change, provider requirement or weakening of managed-app isolation.
+
## 2026-09-17 — Lock-fixture cleanup prevents accumulated test processes
The branch/worktree audit found orphaned `mso-lock-holder` shells and `sleep` children from completed gateway boundary tests. The fixture killed only the forking `flock` parent, leaving the command and inherited lock descriptor alive after its temporary directory was removed. The holder now uses `flock --no-fork` with a single Node process; readiness is inside `try/finally`, and the regression asserts exact PID identity, process exit and kernel-lock reacquisition. No gateway/provider runtime behavior or release guard is changed. Historical process cleanup is restricted to verified orphan fixtures from this conversation's worktrees, not other agents or production processes.