@rubytech/create-sitedesk-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-sitedesk-code",
-  "version": "0.1.606",
+  "version": "0.1.608",
   "description": "Install SiteDesk — automated back office for independent building contractors",
   "bin": {
     "create-sitedesk-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 SiteDesk 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:be3aaf5fcd9b40508ba0a1d0e6b788422dc491432dec1eab64cbe8ce091139e6
+content-hash: sha256:99c51bb52af33450b8add74edc7d5b0876a397e188837ad68dd847e9e1880308
 brand: sitedesk-code
 product-name: SiteDesk
 ---
@@ -2961,6 +2961,41 @@ Telegram profile name and will tell you plainly that it cannot put a name to the
 Ask SiteDesk 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 SiteDesk 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, SiteDesk 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 SiteDesk 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
 SiteDesk'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/telegram/PLUGIN.md

@@ -56,6 +56,10 @@ tools:
     publicAllowlist: false
     adminAllowlist: true
     riskClass: read
+  - name: telegram-instruct
+    publicAllowlist: false
+    adminAllowlist: true
+    riskClass: external
 mcp:
   command: node
   args:
@@ -136,9 +140,9 @@ Two group failures emit nothing on their own and neither reproduces on demand: a
 
 The channel no-event failure is the bot losing its post rights or being removed as an administrator: every later send fails one at a time and nothing announces it. The hourly `[telegram-audit] op=channel-census bots=… channels=… admin=… notAdmin=… noPostRight=…` reconciles it. `noPostRight>0` is a bot that is still an administrator but cannot post, which from the agent's side is indistinguishable from a channel nobody reads.
 
-**What a public bot can send.** A visitor's bot holds four tools: `telegram-card` (text with tappable buttons, a button that opens a page inside Telegram as a Mini App, and edit-in-place by key), `telegram-ask` (polls, quizzes, business checklists, map pins, venues, contact cards, dice), `telegram-media-send` (photo, document, video, audio, voice, animation, video note, 2-10 albums) and `telegram-media-fetch` (opening a file the visitor sent). The other nine stay admin-only: the untyped API passthrough, anything that mutates the bot registry, the bot-wide Mini App menu button, and `telegram-reach`, which lists every chat that has messaged a bot and so would be a cross-visitor read.
+**What a public bot can send.** A visitor's bot holds four tools: `telegram-card` (text with tappable buttons, a button that opens a page inside Telegram as a Mini App, and edit-in-place by key), `telegram-ask` (polls, quizzes, business checklists, map pins, venues, contact cards, dice), `telegram-media-send` (photo, document, video, audio, voice, animation, video note, 2-10 albums) and `telegram-media-fetch` (opening a file the visitor sent). The other ten stay admin-only: the untyped API passthrough, anything that mutates the bot registry, the bot-wide Mini App menu button, `telegram-reach`, which lists every chat that has messaged a bot and so would be a cross-visitor read, and `telegram-instruct`, which steers what an agent says inside another chat and in a visitor's hands would let one visitor put words in an agent's mouth to another.
 
-The other nine are not merely denied on a public spawn — they are never registered, so they are absent from the model's tool list and it cannot spend a visitor's turn calling one. Advertisement and permission are separate gates and this is the first: `PUBLIC_VISIBLE_TOOLS` in `mcp/src/lib/public-pin.ts` is the set, reconciled in both directions against the `publicAllowlist: true` quads above so the two cannot drift. A pinned spawn says what it registered on boot: `[telegram-tools] op=public-surface registered=4 tools=telegram-ask,telegram-card,telegram-media-fetch,telegram-media-send`. Any other name on that line, or a count above four, is the breach — greppable at spawn, with no visitor turn needed to expose it.
+The other ten are not merely denied on a public spawn — they are never registered, so they are absent from the model's tool list and it cannot spend a visitor's turn calling one. Advertisement and permission are separate gates and this is the first: `PUBLIC_VISIBLE_TOOLS` in `mcp/src/lib/public-pin.ts` is the set, reconciled in both directions against the `publicAllowlist: true` quads above so the two cannot drift. A pinned spawn says what it registered on boot: `[telegram-tools] op=public-surface registered=4 tools=telegram-ask,telegram-card,telegram-media-fetch,telegram-media-send`. Any other name on that line, or a count above four, is the breach — greppable at spawn, with no visitor turn needed to expose it.
 
 That line reaches `server.log` through the loopback log-ingest route, so it sits beside the `op=mcp-registered` line for the same spawn. The plugin's stderr does not: it lands in `~/.<brand>/logs/mcp-telegram-<sessionId>.log`, and the spawn-tee mirrors only its own `[mcp-helper]` lifecycle lines onward. When the route cannot take it the plugin says so rather than going quiet — `[telegram-tools] op=public-surface-unposted reason=<no-platform-port|unreachable|status-NNN>` in the per-session file — so an absent census in `server.log` with no `op=public-surface-unposted` anywhere is a spawn that never registered, which is a different fault from a mirror that failed.
 

package/payload/platform/plugins/telegram/mcp/dist/__tests__/card-tool.test.js

@@ -380,7 +380,7 @@ describe("telegramCard — result message id and card-result token (Task 2677)",
         const out = await telegramCard({ botId: BOT, chatId: 222, text: "hi" }, deps(fetchImpl));
         expect(out.outcome).toBe("sent");
         expect(out.messageId).toBe(4242);
-        expect(out.text).toMatch(/card-result: outcome=sent messageId=4242$/);
+        expect(out.text).toMatch(/card-result: outcome=sent messageId=4242 /);
     });
     it("carries the reused id on an edit", async () => {
         const first = recorder([sent(500)]);
@@ -389,7 +389,7 @@ describe("telegramCard — result message id and card-result token (Task 2677)",
         const out = await telegramCard({ botId: BOT, chatId: 222, key: "j", text: "two" }, deps(second.fetchImpl));
         expect(out.outcome).toBe("edited");
         expect(out.messageId).toBe(500);
-        expect(out.text).toMatch(/card-result: outcome=edited messageId=500$/);
+        expect(out.text).toMatch(/card-result: outcome=edited messageId=500 /);
     });
     it("emits messageId=none and no id on a refused send", async () => {
         const { fetchImpl } = recorder([
@@ -398,7 +398,7 @@ describe("telegramCard — result message id and card-result token (Task 2677)",
         const out = await telegramCard({ botId: BOT, chatId: 222, text: "hi" }, deps(fetchImpl));
         expect(out.outcome).toBe("none");
         expect(out.messageId).toBeUndefined();
-        expect(out.text).toMatch(/card-result: outcome=none messageId=none$/);
+        expect(out.text).toMatch(/card-result: outcome=none messageId=none /);
     });
     it("does not append a token when the card never reached Telegram (unknown bot)", async () => {
         const { fetchImpl } = recorder([]);
@@ -406,6 +406,38 @@ describe("telegramCard — result message id and card-result token (Task 2677)",
         expect(out.text).not.toContain("card-result:");
     });
 });
+// Task 2723 — the bot and chat the card was ACTUALLY sent to. The follower keys
+// the operator-surface store row on these, so a card the admin door sends into
+// another chat is filed in that chat's conversation rather than the sender's.
+describe("telegramCard — the trailer names the destination (Task 2723)", () => {
+    it("names the bot and chat the card was sent to", async () => {
+        const { fetchImpl } = recorder([sent(4242)]);
+        const out = await telegramCard({ botId: BOT, chatId: 222, text: "hi" }, deps(fetchImpl));
+        expect(out.text).toMatch(/card-result: outcome=sent messageId=4242 botId=111 chatId=222$/);
+    });
+    it("names them on an edit too, so the patch reaches the same conversation", async () => {
+        const first = recorder([sent(500)]);
+        await telegramCard({ botId: BOT, chatId: 222, key: "j", text: "one" }, deps(first.fetchImpl));
+        const second = recorder([sent(500)]);
+        const out = await telegramCard({ botId: BOT, chatId: 222, key: "j", text: "two" }, deps(second.fetchImpl));
+        expect(out.text).toMatch(/card-result: outcome=edited messageId=500 botId=111 chatId=222$/);
+    });
+    it("carries the PINNED pair, not the one the model supplied", async () => {
+        // Through runPinned, which is the only path a public spawn's card takes:
+        // applyPublicPin overwrites both fields before telegramCard is entered, so
+        // reading the supplied input here would record the model's guess.
+        const { fetchImpl } = recorder([sent(9)]);
+        const out = await runPinned("telegram-card", { botId: "999", chatId: 777, text: "hi" }, telegramCard, () => ({ ...deps(fetchImpl), publicPin: { botId: BOT, chatId: "222" } }));
+        expect(out.content[0].text).toMatch(/card-result: outcome=sent messageId=9 botId=111 chatId=222$/);
+    });
+    it("names them on a refused send as well, alongside messageId=none", async () => {
+        const { fetchImpl } = recorder([
+            { ok: false, error_code: 403, description: "Forbidden: bot was blocked by the user" },
+        ]);
+        const out = await telegramCard({ botId: BOT, chatId: 222, text: "hi" }, deps(fetchImpl));
+        expect(out.text).toMatch(/card-result: outcome=none messageId=none botId=111 chatId=222$/);
+    });
+});
 // Task 2677 — a keyed card whose stored id sits below the chat's newest inbound id
 // is buried above the customer's later messages, so it is deleted and reposted at
 // the bottom. A refused delete falls back to edit-in-place.