@rubytech/create-realagent-code 0.1.606 → 0.1.608

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-realagent-code",
-  "version": "0.1.606",
+  "version": "0.1.608",
   "description": "Install Real Agent — Built for agents. By agents.",
   "bin": {
     "create-realagent-code": "./dist/index.js"

package/payload/platform/lib/admins-write/vitest.config.ts

@@ -7,6 +7,7 @@ import { defineConfig } from "vitest/config";
 // is actually on disk.
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["__tests__/**/*.test.ts"],

package/payload/platform/lib/agent-dispatch-rule/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/brand-templating/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/canonical-instant/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/dispatch-read/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/graph-search/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from 'vitest/config';
 
 export default defineConfig({
   test: {
+    setupFiles: ['../../test/tmpdir-setup.ts'],
     environment: 'node',
     globals: false,
     include: ['src/__tests__/**/*.test.ts'],

package/payload/platform/lib/graph-style/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/mcp-lifeline/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/routine-templates/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/task-secrets/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from 'vitest/config';
 
 export default defineConfig({
   test: {
+    setupFiles: ['../../test/tmpdir-setup.ts'],
     environment: 'node',
     globals: false,
     include: ['src/__tests__/**/*.test.ts'],

package/payload/platform/lib/telegram-button-labels/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/telegram-managed-bot/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/telegram-media/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/telegram-reach/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/lib/telegram-store-read/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../test/tmpdir-setup.ts"],
     environment: "node",
     globals: false,
     include: ["src/__tests__/**/*.test.ts"],

package/payload/platform/plugins/admin/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     testTimeout: 10_000,

package/payload/platform/plugins/admin/skills/platform-architecture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: platform-architecture
 description: Use when grounding any documented-surface claim about what Real Agent ships — plugins, skills, specialists, install/deploy flows, internals. This is the install catalogue, not evidence of what is enabled on the current account. For install state on this account, call `capabilities-here`; for documented surface, cite the `Source:` URL inline.
-content-hash: sha256:72ceb87984dc863b94b0bb40ef8aead338b2d093e44caf456504d6d09ea0a2c6
+content-hash: sha256:91d181f269c43daa00e505bc526da955baa0aa8df0a096c7c4e23c31afb58200
 brand: realagent-code
 product-name: Real Agent
 ---
@@ -2961,6 +2961,41 @@ Telegram profile name and will tell you plainly that it cannot put a name to the
 Ask Real Agent to save the Telegram ID against the contact. It is one change to one contact, and
 it takes effect on the very next message.
 
+## Correcting what a public agent told a visitor
+
+When one of your public bots tells a visitor something wrong, the fix is to instruct the agent that
+is talking to them, not to message the visitor yourself.
+
+The reason is worth understanding, because the obvious approach quietly fails. Every conversation is
+its own separate agent with its own memory. If you send the visitor a correction from your chat, they
+receive it, but the agent that has been talking to them never sees it: it is a different
+conversation, and nothing carries a message from yours into theirs. It carries on from what it
+believes, and repeats the mistake on the next question. That is exactly what happened on a live
+conversation where a corrected price was quoted wrong again ninety-seven seconds later.
+
+So tell Real Agent what the visitor should be told, and name the bot and the chat: "Tell the
+visitor on chat 1234567890 that the price is 75, not 65." The instruction goes into that visitor's
+own conversation. The agent writes the message itself, in the same voice it has been using, and its
+own memory now holds what it said, so it will not contradict it a moment later. The visitor sees a
+normal message from the assistant they have been talking to, with no sign that anybody stepped in.
+
+Write the intent rather than the exact sentence. This is an instruction to the agent, not text
+delivered word for word, so "tell them we can do Thursday morning but not the afternoon" works better
+than a script.
+
+Four situations are refused, and each one says why rather than failing quietly:
+
+- The bot is not a public bot. Your own admin bot and any specialist bot are conversations with your
+  own side, not with a visitor, so there is nothing to instruct.
+- The agent has been switched off. Nothing is resurrected behind your back; turn it back on, or
+  message the person yourself.
+- The chat belongs to a connected business account. Those conversations are held separately and this
+  route cannot reach them.
+- The chat is a broadcast channel the bot does not allow. A channel post reaches every subscriber and
+  cannot be unsent.
+
+If you need the chat ID, ask "who can you reach on Telegram?" first.
+
 ## Getting a Chat ID
 
 To message a specific person or group, Real Agent needs their chat ID. The easiest way:
@@ -3047,7 +3082,9 @@ it puts the answer in the card itself and does not add a sentence beside it. On
 public bot, that following sentence is held back on purpose, so the visitor sees
 the card once and not the same thing twice. And when someone presses a button,
 your conversation view shows the button's own wording — "1 passenger", "One way"
-— rather than the code behind it.
+— rather than the code behind it. A card Real Agent sends into a different
+chat appears in that chat's conversation, where the person who received it is,
+and not in the conversation you asked for it from.
 
 The same is now true of most of what Telegram sends. Reply to one of
 Real Agent's messages and it sees the message you replied to, so "yes, do

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

@@ -9,6 +9,16 @@ 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-15 (0.1.608)
+
+- You can now steer a public agent while it is mid-conversation with someone, rather than waiting for the exchange to end.
+- A card sent into a different chat is filed in that chat, not in the conversation of whoever sent it.
+- Routines already running on your installs now use the work-check gates added over the past week. They kept their old always-run behaviour until this backfill, and routines left behind with nothing to run are removed.
+
+## 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/platform/plugins/aeo/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     testTimeout: 10_000,

package/payload/platform/plugins/cloudflare/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["__tests__/**/*.test.ts"],
     exclude: process.env.RUN_LIVE === "1" ? [] : ["__tests__/live/**"],

package/payload/platform/plugins/connector/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
   },

package/payload/platform/plugins/contacts/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     // Scoped to src, matching plugins/telegram/mcp: without it vitest also
     // collects dist/__tests__/*.test.js, which `tsc -p` emits because this

package/payload/platform/plugins/docs/references/telegram-guide.md

@@ -138,6 +138,41 @@ Telegram profile name and will tell you plainly that it cannot put a name to the
 Ask {{productName}} to save the Telegram ID against the contact. It is one change to one contact, and
 it takes effect on the very next message.
 
+## Correcting what a public agent told a visitor
+
+When one of your public bots tells a visitor something wrong, the fix is to instruct the agent that
+is talking to them, not to message the visitor yourself.
+
+The reason is worth understanding, because the obvious approach quietly fails. Every conversation is
+its own separate agent with its own memory. If you send the visitor a correction from your chat, they
+receive it, but the agent that has been talking to them never sees it: it is a different
+conversation, and nothing carries a message from yours into theirs. It carries on from what it
+believes, and repeats the mistake on the next question. That is exactly what happened on a live
+conversation where a corrected price was quoted wrong again ninety-seven seconds later.
+
+So tell {{productName}} what the visitor should be told, and name the bot and the chat: "Tell the
+visitor on chat 1234567890 that the price is 75, not 65." The instruction goes into that visitor's
+own conversation. The agent writes the message itself, in the same voice it has been using, and its
+own memory now holds what it said, so it will not contradict it a moment later. The visitor sees a
+normal message from the assistant they have been talking to, with no sign that anybody stepped in.
+
+Write the intent rather than the exact sentence. This is an instruction to the agent, not text
+delivered word for word, so "tell them we can do Thursday morning but not the afternoon" works better
+than a script.
+
+Four situations are refused, and each one says why rather than failing quietly:
+
+- The bot is not a public bot. Your own admin bot and any specialist bot are conversations with your
+  own side, not with a visitor, so there is nothing to instruct.
+- The agent has been switched off. Nothing is resurrected behind your back; turn it back on, or
+  message the person yourself.
+- The chat belongs to a connected business account. Those conversations are held separately and this
+  route cannot reach them.
+- The chat is a broadcast channel the bot does not allow. A channel post reaches every subscriber and
+  cannot be unsent.
+
+If you need the chat ID, ask "who can you reach on Telegram?" first.
+
 ## Getting a Chat ID
 
 To message a specific person or group, {{productName}} needs their chat ID. The easiest way:
@@ -224,7 +259,9 @@ it puts the answer in the card itself and does not add a sentence beside it. On
 public bot, that following sentence is held back on purpose, so the visitor sees
 the card once and not the same thing twice. And when someone presses a button,
 your conversation view shows the button's own wording — "1 passenger", "One way"
-— rather than the code behind it.
+— rather than the code behind it. A card {{productName}} sends into a different
+chat appears in that chat's conversation, where the person who received it is,
+and not in the conversation you asked for it from.
 
 The same is now true of most of what Telegram sends. Reply to one of
 {{productName}}'s messages and it sees the message you replied to, so "yes, do

package/payload/platform/plugins/email/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     testTimeout: 10_000,

package/payload/platform/plugins/filesystem/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     include: ["src/**/__tests__/**/*.test.ts"],
     environment: "node",
   },

package/payload/platform/plugins/graph-viewer/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     include: ["src/**/*.test.ts"],
     environment: "node",
   },

package/payload/platform/plugins/memory/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     // narrow to `src/tools/__tests__/` so vitest does not pick up
     // pre-existing `src/lib/__tests__/` files that use Node's built-in

package/payload/platform/plugins/scheduling/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     testTimeout: 10_000,

package/payload/platform/plugins/storage-broker/mcp/vitest.config.ts

@@ -1,4 +1,9 @@
 import { defineConfig } from "vitest/config";
 export default defineConfig({
-  test: { environment: "node", include: ["src/**/__tests__/**/*.test.ts"], testTimeout: 10_000 },
+  test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
+    environment: "node",
+    include: ["src/**/__tests__/**/*.test.ts"],
+    testTimeout: 10_000,
+  },
 });

package/payload/platform/plugins/url-get/mcp/vitest.config.ts

@@ -7,6 +7,7 @@ import { defineConfig } from "vitest/config";
 // and this flag becomes a no-op.
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     passWithNoTests: true,

package/payload/platform/plugins/whatsapp/mcp/vitest.config.ts

@@ -2,6 +2,7 @@ import { defineConfig } from "vitest/config";
 
 export default defineConfig({
   test: {
+    setupFiles: ["../../../test/tmpdir-setup.ts"],
     environment: "node",
     include: ["src/**/__tests__/**/*.test.ts"],
     testTimeout: 10_000,