switchroom 0.19.10 → 0.19.11

package/dist/cli/switchroom.js

@@ -2120,7 +2120,7 @@ var init_esm = __esm(() => {
 });
 
 // src/build-info.ts
-var VERSION = "0.19.10", COMMIT_SHA = "d88584dd";
+var VERSION = "0.19.11", COMMIT_SHA = "cd60a0c0";
 
 // src/cli/resolve-version.ts
 import { existsSync, readFileSync } from "node:fs";
@@ -29506,15 +29506,25 @@ You're writing for a phone screen in Telegram. Every reply renders as rich Markd
 
 - **Short answers (a line or two): plain prose, no formatting.** "on it, pulling the
   logs now" is already perfect. No bold, no bullets, no headings.
-- **Default: light structure.** Bold ONLY the one key fact or answer, never more. A
+- **Default: light structure.** Bold ONLY the one key fact or answer, never more.
+  *Italic* for a light aside or a term of art \u2014 rarer than bold; if everything is
+  emphasised, nothing is. ~~Strikethrough~~ only for a genuine retraction or a
+  "was X, now Y" \u2014 never decoration. A
   list only for 3+ genuinely parallel items the reader will scan or compare; two items
-  or a flowing thought stay prose. \`code spans\` for identifiers: filenames, commands,
+  or a flowing thought stay prose. A numbered list ONLY when order carries meaning
+  (steps to follow, a ranking); a nested sub-list only for a real hierarchy, one level
+  deep. \`code spans\` for identifiers: filenames, commands,
   config keys, error codes (tap-to-copy). Wrap dynamic identifiers in backticks:
   code-span content is literal, so it never needs escaping. Links as \`[label](url)\`,
   never bare pasted URLs mid-prose.
 - **Long answers may add the rich constructs, but only when they cut the reader's
   effort:** a GFM pipe table for real 2-D data (rows x columns); headings only in a
-  multi-section answer; \`>\` for quoted text; fenced code blocks ALWAYS with a language
+  multi-section answer; a \`---\` divider only between genuinely separate sections of a
+  long answer (a heading usually does the job alone); \`>\` for quoted text; a spoiler
+  \`||text||\` ONLY when the reader should opt in before seeing it (a punchline, a plot
+  detail, a shock number) \u2014 never for emphasis; \`==highlight==\` to marker-pen the one
+  decisive phrase inside a longer passage \u2014 rarer than bold, never stacked with it;
+  fenced code blocks ALWAYS with a language
   hint (\`\`\`diff, \`\`\`json, \`\`\`bash \u2014 bare fence only for non-code fixed-width output);
   and the flagship \u2014 the **expandable blockquote** \`**> first line\` + \`> continuation\`
   for a long quote, stack trace, or detailed aside the reader can collapse. Use it
@@ -29525,8 +29535,9 @@ Renders wrong on this path \u2014 never emit: underline (\`__x__\` renders as bo
 
 The framework normalizes mechanics in code on every outbound message: block spacing,
 em/en dashes, and \`\u2022\` bullet markers are
-rewritten deterministically; unsupported tokens (\`^highlight^\`, \`$math$\`, \`<details>\`,
-footnotes) are repaired; long messages are chunked safely at 32768 chars (fences and
+rewritten deterministically; unsupported tokens (the CARET \`^highlight^\` form \u2014
+\`==highlight==\` renders fine \u2014 plus \`$math$\`, \`<details>\`, footnotes) are repaired;
+long messages are chunked safely at 32768 chars (fences and
 table rows never bisected); over-bolded messages get their bold stripped. Don't
 hand-tune spacing or fight it \u2014 write the content, the gateway makes typography
 consistent. Long before the cap, ask whether a wall of text is the right answer at all.

package/dist/host-control/main.js

@@ -26664,7 +26664,7 @@ import { existsSync as existsSync9, readFileSync as readFileSync7 } from "node:f
 import { dirname as dirname5, join as join7 } from "node:path";
 
 // src/build-info.ts
-var VERSION = "0.19.10";
+var VERSION = "0.19.11";
 
 // src/cli/resolve-version.ts
 function readPackageVersion() {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "switchroom",
   "//version": "NOT the release version — source of truth is the git tag, resolved by scripts/build.mjs:resolveVersion() (see CLAUDE.md > Standard release process). This field is stale by design and only the Layer-4 dev/non-tag fallback for build.mjs + src/cli/resolve-version.ts; do NOT bump it expecting a release to pick it up. npm-pack tarball naming needs a real version — do that as an UNCOMMITTED pack-time bump (see release step 6), never a committed one.",
-  "version": "0.19.10",
+  "version": "0.19.11",
   "description": "Run Claude Code 24/7 on your Claude Pro/Max subscription over Telegram. Open-source alternative to OpenClaw and NanoClaw — no API keys.",
   "type": "module",
   "bin": {

package/telegram-plugin/dist/gateway/gateway.js

@@ -93614,10 +93614,10 @@ function startGatewayHeartbeat(stateDir, intervalMs = GATEWAY_HEARTBEAT_INTERVAL
 }
 
 // ../src/build-info.ts
-var VERSION = "0.19.10";
-var COMMIT_SHA = "d88584dd";
-var COMMIT_DATE = "2026-07-21T11:39:08Z";
-var LATEST_PR = 3495;
+var VERSION = "0.19.11";
+var COMMIT_SHA = "cd60a0c0";
+var COMMIT_DATE = "2026-07-21T21:06:25Z";
+var LATEST_PR = 3497;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts