@rubytech/create-maxy-code 0.1.606 → 0.1.607

package/dist/index.js

@@ -3,7 +3,7 @@ import { execFileSync, spawn, spawnSync } from "node:child_process";
 import { existsSync, mkdirSync, writeFileSync, cpSync, readFileSync, rmSync, readdirSync, appendFileSync, openSync, closeSync, chmodSync, statSync, realpathSync, accessSync, constants as fsConstants } from "node:fs";
 import { clearBrandAgentRoot } from "./brand-agent-root.js";
 import { seedBypassPermissionsSettings, assertBypassPermissionsSeed } from "./permissions-seed.js";
-import { resolve, join, dirname } from "node:path";
+import { resolve, join, dirname, basename } from "node:path";
 import { randomBytes } from "node:crypto";
 import { resolveInstallPortFromFs, buildMaxyUnitFile, buildClaudeSessionManagerUnitFile, buildEmailSamplerUnitFile, buildClaudePtysSliceUnitFile, buildCloudflaredSliceUnitFile, buildDarwinServiceEnvPath } from "./port-resolution.js";
 import { buildBrandCronBlock, mergeBrandCronBlock } from "./cron-registration.js";
@@ -570,6 +570,7 @@ function ensureNonSnapChromium() {
         }
         RESOLVED_CHROMIUM_BIN = decision.resolvedPath;
     }
+    RESOLVED_CHROMIUM_BIN = preferUnwrappedChromium(RESOLVED_CHROMIUM_BIN);
     // Defensive: never persist a snap-confined path. If realpath of the resolved
     // binary still lands under /snap/ (e.g. apt landed a snap package by mistake
     // on a misconfigured device), throw before writeChromiumBinaryPathFile sees
@@ -622,6 +623,44 @@ function runChromiumPostInstallGate(chromiumBin) {
     console.log("  Chromium post-install gate passed.");
     logFile(`  [snap-chromium] post-install gate ok: ${chromiumBin} exit=0`);
 }
+/**
+ * Prefer the real Chromium ELF binary over a distro shell wrapper.
+ *
+ * Debian and Raspberry Pi OS ship `/usr/bin/chromium` as a POSIX shell script
+ * that appends its own flags and then `exec $LIBDIR/$APPNAME "$@"`, where
+ * `LIBDIR=/usr/lib/$APPNAME` — so the real binary is derivable from the
+ * wrapper's own layout rather than guessed.
+ *
+ * On aarch64 with a page size above 4096 that wrapper adds
+ * `--js-flags=--no-decommit-pooled-pages` (its workaround for Debian #1089647).
+ * Current Chromium's V8 has removed that flag, so V8 exits "unrecognized flag",
+ * the GPU process dies with it, and the installer's CDP check then correctly
+ * finds nothing listening and aborts the upgrade. Measured on the beacons Pi
+ * 2026-08-14: Chromium 148.0.7778.167, `getconf PAGESIZE` 16384, and
+ * `chromium --js-flags=--no-decommit-pooled-pages` reproduces it directly.
+ *
+ * Execing the binary skips the wrapper and every flag it would inject. The
+ * wrapper is returned unchanged whenever the shape does not match — not a
+ * script, no binary at the derived path, or that path is not ELF — so a distro
+ * laying Chromium out differently is untouched.
+ */
+function preferUnwrappedChromium(binPath) {
+    const fileType = (p) => {
+        const r = spawnSync("file", ["-b", p], { encoding: "utf-8", stdio: "pipe", timeout: 5_000 });
+        return r.status === 0 ? (r.stdout ?? "").trim() : "";
+    };
+    if (!/shell script/i.test(fileType(binPath)))
+        return binPath;
+    const appName = basename(binPath);
+    const real = `/usr/lib/${appName}/${appName}`;
+    if (!existsSync(real) || !/^ELF/.test(fileType(real))) {
+        logFile(`  [chromium-wrapper] ${binPath} is a wrapper but ${real} is not a usable binary — keeping the wrapper`);
+        return binPath;
+    }
+    console.log(`  Chromium wrapper bypassed: ${binPath} → ${real}`);
+    logFile(`  [chromium-wrapper] bypassed wrapper=${binPath} binary=${real}`);
+    return real;
+}
 /**
  * write the resolved Chromium absolute path to
  * `<INSTALL_DIR>/platform/config/chromium-binary.path` so vnc.sh and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.606",
+  "version": "0.1.607",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/plugins/admin/skills/whats-new/SKILL.md

@@ -9,6 +9,10 @@ Invoked by the admin agent directly.
 
 This is the platform's release timeline, newest first. Each entry shows the date it shipped and the version it shipped in, so you can tell the operator how current their install is. To compare, read the installed version from `capabilities-here` and match it against the versions below. Keep answers high level and in plain English; this is a summary, not a full commit log.
 
+## 2026-08-14 (0.1.607)
+
+- Upgrades no longer fail on a Raspberry Pi with a 16K page size. The system's own Chromium launcher adds a setting that current Chromium has removed, so the browser exited on startup and the install stopped when it could not reach it. The installer now runs Chromium directly, skipping that launcher.
+
 ## 2026-08-14 (0.1.606)
 
 - Conversations start after an install again. The installer marked only your home folder as trusted, and the assistant now asks about the folder each account actually runs from, so a session would stop at a trust prompt nobody could answer.

package/payload/server/public/operator.html

@@ -22,8 +22,8 @@
   <link rel="modulepreload" crossorigin href="/assets/wrench-nDMQ6x-6.js">
   <link rel="modulepreload" crossorigin href="/assets/page-B72XigcU.js">
   <link rel="stylesheet" crossorigin href="/assets/jsx-runtime-hPFGo4rC.css">
-  <link rel="stylesheet" crossorigin href="/assets/useMediaQuery-DXAuc8G-.css">
   <link rel="stylesheet" crossorigin href="/assets/AdminLoginScreens-CWMpccrR.css">
+  <link rel="stylesheet" crossorigin href="/assets/useMediaQuery-DXAuc8G-.css">
   <link rel="stylesheet" href="/brand-defaults.css">
 </head>
 <body>