create-pmos 0.60.0 → 0.60.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.60.0",
+  "version": "0.60.1",
   "description": "Scaffold the PMOS portable kit — run the PMOS product-management workflow (initiative → lane-fit spec → contract → build → three gates, with work-type lanes for features, research, maintenance, incidents, and content) entirely inside your own repo, with all state as git-versioned files. Includes `workflow-sweep`, which audits the state every board derives from and separates real defects from work you simply have not done. `create-pmos workspace` also installs + launches the local Terminal Workspace GUI. No database, no network, no telemetry.",
   "license": "MIT",
   "bin": {

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@45d7d1e
+kernel-source: pmos@63010ef
 assembled: 2026-10-06
 mode: vendor

package/payload/planning/evals/eval-calibration.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Eval calibration log"
 description: "Append-only record of every PM override of an evaluator verdict."
-generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:28:53Z"}
 status: stable
 ---
 

package/payload/planning/okrs/health-budgets.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Health budgets"
 description: "Closed registry of health-budget anchors (D59), edited only by the PM."
-generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:28:53Z"}
 status: stable
 ---
 

package/payload/state/discoveries.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Discoveries and friction log"
 description: "Append-only record of what runs discovered and where the process rubbed."
-generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:28:53Z"}
 status: stable
 ---
 

package/workspace/guide/layout.md

@@ -35,7 +35,7 @@ Settings holds settings only, in seven sections:
 - **Theme**: Dark or Light.
 - **Updates**: the version of the workspace app and the version of the kit in the current repository. Press **Check for updates** to compare them with the latest published version of PMOS. This is the only time the workspace asks the internet for a version, and it asks only when you press. When a newer version is available, a button shows for each part that is older:
   - **Update the kit** does what `npx create-pmos@latest --update` does in a terminal. It changes only the kit's own files under `pmos/` (skills, scripts, templates and guides). Your records in `state/`, `planning/` and `okf/product/` do not change. The last lines of the output show under the button. The changed files are under `pmos/`, which Sync treats as records, so Sync (or automatic sync) sends them with your other records. To read them first, look at `git diff pmos/` before you sync.
-  - **Update the workspace** does what `pmos upgrade` does in a terminal. It asks you first. The workspace stops, installs the new version and starts again, and the page reloads when the new version starts. Sessions keep running in tmux. Press it on the computer that runs the workspace. From a phone it is refused, because the phone cannot see the restart through. When the workspace runs from a PMOS checkout, update it with `git pull` instead.
+  - **Update the workspace** does what `pmos upgrade` does in a terminal. It asks you first. The workspace stops, installs the new version and starts again, and the page reloads when the new version starts. Sessions keep running in tmux. It works on the computer that runs the workspace and at its Online address, because the page comes back there after the restart. It also works on a phone or public address that signs in with a token set in `PMOS_TOKEN`, which the workspace keeps. When the workspace made its own token at start, the token changes on the restart, so the page refuses and says where to press it. When the workspace runs from a PMOS checkout, update it with `git pull` instead.
 
 Your work is never in Settings. It is in Agenda, Initiatives, Board and Reports.
 

package/workspace/lib/kit-update.js

@@ -7,6 +7,7 @@
  *   compare(st, latestVersion)              → { appBehind, kitBehind }
  *   updateKit(root, { version, exec })      → Promise<{ ok, output, kit } | { ok:false, error, output }>
  *   upgradeApp(root, { version, logFile, spawn }) → { ok, log } | { ok:false, error }
+ *   whereFrom({ desktop, onlineHost, tokenKept })  → { ok } | { ok:false, error }   may this page start the app update?
  *
  * The page does what the terminal does, and nothing more. Each action runs the command the README tells the PM to type:
  *   check        npm view create-pmos version
@@ -133,6 +134,19 @@ async function updateKit(root, { version, exec = cp.execFile } = {}) {
   return { ok: true, output, kit: readKit(root) };
 }
 
+/**
+ * May the page that pressed Update the workspace start it? The update stops this server and starts a new one with the
+ * same environment (create-pmos and the pmos launcher pass it on), so the page can come back when its way in survives:
+ *   desktop     a direct loopback request on the computer that runs the workspace
+ *   onlineHost  the Online address (D89): the switch is kept in the state folder and the Access sign-in is the edge's
+ *   tokenKept   a phone or public address signed in with a token set in PMOS_TOKEN: the new server keeps that token
+ * A token the server generated at start is new after the restart, so a page signed in with it cannot come back.
+ */
+function whereFrom({ desktop = false, onlineHost = false, tokenKept = false } = {}) {
+  if (desktop || onlineHost || tokenKept) return { ok: true };
+  return { ok: false, error: 'This page signed in with a token that changes when the workspace restarts, so it could not come back. Update the workspace on the computer it runs on, or at its Online address' };
+}
+
 /**
  * Start the app reinstall and return at once. The child is detached from this server, because create-pmos stops this
  * server before it reinstalls, and it starts the new one after. Its output goes to `logFile`.
@@ -158,4 +172,4 @@ function upgradeApp(root, { version, logFile, spawn = cp.spawn } = {}) {
   }
 }
 
-module.exports = { PKG_NAME, cmpVer, validVersion, readKit, fromCheckout, status, compare, latest, updateKit, upgradeApp };
+module.exports = { PKG_NAME, cmpVer, validVersion, readKit, fromCheckout, status, compare, latest, updateKit, upgradeApp, whereFrom };

package/workspace/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "pmos-workspace",
-  "version": "0.60.0",
+  "version": "0.60.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {

package/workspace/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmos-workspace",
-  "version": "0.60.0",
+  "version": "0.60.1",
   "private": true,
   "description": "PMOS Terminal Workspace — local companion hosting real PTYs beside the library and gates (D62)",
   "license": "MIT",

package/workspace/server.js

@@ -7017,11 +7017,14 @@ async function handleRequest(req, res) {
         return json(res, { ws: w.id, ...r, ...st() }, r.ok ? 200 : 502);
       } finally { kitBusy = null; }
     }
-    // The app update stops this server and starts a new one. It is refused from a phone: the new server starts on
-    // loopback only, so the phone that asked would lose the page. It is refused from a checkout, which git updates.
-    if (!remoteAccess.isLoopbackAddr(req.socket.remoteAddress) || remoteAccess.isProxied(req.headers, BIND.publicHost)) {
-      return json(res, { ok: false, error: 'Update the workspace from the computer it runs on' }, 403);
-    }
+    // The app update stops this server and starts a new one, so the page must be able to come back (kitUpdate.whereFrom).
+    // It is refused from a checkout, which git updates.
+    const where = kitUpdate.whereFrom({
+      desktop: remoteAccess.isLoopbackAddr(req.socket.remoteAddress) && !remoteAccess.isProxied(req.headers, publicHost()),
+      onlineHost: viaOnlineHost(req.headers),
+      tokenKept: !!TOKEN && !BIND.generated,
+    });
+    if (!where.ok) return json(res, { ok: false, error: where.error }, 403);
     if (st().app.fromCheckout) return json(res, { ok: false, error: 'This workspace runs from a PMOS checkout. Update it with git pull' }, 409);
     const r = kitUpdate.upgradeApp(w.root, { version: body.version, logFile: path.join(STATE, 'app-update.log') });
     if (!r.ok) return json(res, { ok: false, error: r.error }, 400);