switchroom 0.14.71 → 0.14.72

package/dist/cli/switchroom.js

@@ -49601,8 +49601,8 @@ var {
 } = import__.default;
 
 // src/build-info.ts
-var VERSION = "0.14.71";
-var COMMIT_SHA = "314a0e0e";
+var VERSION = "0.14.72";
+var COMMIT_SHA = "0e840d59";
 
 // src/cli/agent.ts
 init_source();
@@ -52178,7 +52178,7 @@ function buildSettingsHooksBlock(p) {
 
 ` + "GROUND BEFORE YOU ASSERT. Any fact in your reply that can change " + "(a number, a status, a price, a date, who-uses-what, anything " + '"current" or "latest") must come from a source you actually checked ' + "THIS turn: your data tool, a file, the web. Memory and what you " + '"already know" are leads to verify, not sources. If you have not ' + "checked it this turn, do not state it as fact: go get it now, or tell " + "the user you will confirm and then do it. A confident wrong number is " + `worse than "let me check".
 
-` + "VOICE: write like a sharp colleague, not a chatbot. Do not open with " + `affirmation ("You're absolutely right", "Great question", "Great ` + 'catch", "Exactly!"); just answer. Skip AI-tell filler ("smoking ' + `gun", "delve", "it's worth noting", "a testament to", "in today's ` + 'fast-paced..."). Lead with the answer, plain words, kept short. When ' + `the user is wrong, say so directly; flattery is not help.
+` + "VOICE: write like a sharp colleague, not a chatbot. Lead with the " + "answer, plain words, plain punctuation (commas and periods, not " + `em-dashes). Skip the hollow openers ("You're absolutely right", ` + '"Great question", "Great catch", "Exactly!") and AI-tell filler ' + `("smoking gun", "delve", "it's worth noting", "a testament to", "in ` + `today's fast-paced..."). Genuine acknowledgement is fine when it is ` + 'real and adds something ("good catch, that was my bug"); what to ' + "avoid is the reflexive praise that opens every reply and means " + "nothing. When the user is wrong, say so directly; flattery is not " + `help.
 
 ` + 'CRITICAL: "answer" means a call to the reply tool ' + "(mcp__switchroom-telegram__reply, or stream_reply with done=true). " + "Your terminal/transcript text is NEVER delivered to Telegram \u2014 the " + "user sees only what you send through the reply tool. After a long " + "tool sequence (scheduling, multi-step research, sub-agent handback), " + "do not let your closing narration stand as the answer: end the turn " + "by passing that narration to the reply tool. No reply tool call = the " + "user got nothing, however much text you wrote. Call the reply tool as " + "your FIRST action when you have the answer \u2014 do not write it out as " + "transcript text first and call reply afterward: a framework backstop " + "flushes unsent text after a delay and then your real reply lands late " + "and out of order.</turn-pacing>";
   const switchroomUserPromptSubmit = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "switchroom",
-  "version": "0.14.71",
+  "version": "0.14.72",
   "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

@@ -42543,6 +42543,10 @@ function enabled4() {
   const v = process.env.SWITCHROOM_DISABLE_VOICE_SCRUB;
   return !(v === "1" || v === "true");
 }
+function openerStripEnabled() {
+  const v = process.env.SWITCHROOM_VOICE_STRIP_OPENERS;
+  return v === "1" || v === "true";
+}
 var LEADING_AFFIRMATION_RE = /^(\s*)(you(?:['\u2019]| a)re absolutely right|you(?:['\u2019]| a)re so right|you(?:['\u2019]| a)re absolutely correct|absolutely right|exactly right|great catch|good catch|nice catch|spot on)\b(?:\s*$|\s*[!.,;:\u2014\u2013-][\s!.,;:\u2014\u2013-]*)/i;
 function stripLeadingAffirmation(text) {
   const m = LEADING_AFFIRMATION_RE.exec(text);
@@ -42620,7 +42624,7 @@ function scrubVoice(text) {
     return { scrubbed: text, replaced: 0, openersStripped: 0 };
   }
   const { parked, parts } = park(text);
-  const opener = stripLeadingAffirmation(parked);
+  const opener = openerStripEnabled() ? stripLeadingAffirmation(parked) : { out: parked, count: 0 };
   const { out, replaced } = replaceDashes(opener.out);
   const total = replaced + opener.count;
   if (total === 0) {
@@ -52815,10 +52819,10 @@ function sweepStaleTurnActiveMarker(stateDir, opts) {
 }
 
 // ../src/build-info.ts
-var VERSION = "0.14.71";
-var COMMIT_SHA = "314a0e0e";
-var COMMIT_DATE = "2026-06-05T14:23:58Z";
-var LATEST_PR = 2181;
+var VERSION = "0.14.72";
+var COMMIT_SHA = "0e840d59";
+var COMMIT_DATE = "2026-06-06T00:39:32Z";
+var LATEST_PR = 2183;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts

package/telegram-plugin/tests/text-voice-scrub.test.ts

@@ -173,12 +173,17 @@ describe('scrubVoice — em / en dash replacement', () => {
   })
 })
 
-describe('scrubVoice — leading sycophancy openers', () => {
+describe('scrubVoice — leading sycophancy openers (opt-in backstop)', () => {
+  // The opener strip is OFF by default (tone is the prompt's job); these
+  // tests opt it in to exercise the mechanism that remains available via
+  // SWITCHROOM_VOICE_STRIP_OPENERS=1.
   beforeEach(() => {
     delete process.env.SWITCHROOM_DISABLE_VOICE_SCRUB
+    process.env.SWITCHROOM_VOICE_STRIP_OPENERS = '1'
   })
   afterEach(() => {
     delete process.env.SWITCHROOM_DISABLE_VOICE_SCRUB
+    delete process.env.SWITCHROOM_VOICE_STRIP_OPENERS
   })
 
   it('strips a leading "You\'re absolutely right" and recapitalizes', () => {
@@ -261,3 +266,43 @@ describe('scrubVoice — leading sycophancy openers', () => {
     expect(r.openersStripped).toBe(0)
   })
 })
+
+describe('scrubVoice — opener strip is OFF by default (prompt carries tone)', () => {
+  // No SWITCHROOM_VOICE_STRIP_OPENERS set: the deterministic layer must
+  // NOT delete words. Em-dash normalization (punctuation, no content
+  // removed) still runs. Tone is the prompt VOICE directive's job.
+  beforeEach(() => {
+    delete process.env.SWITCHROOM_DISABLE_VOICE_SCRUB
+    delete process.env.SWITCHROOM_VOICE_STRIP_OPENERS
+  })
+  afterEach(() => {
+    delete process.env.SWITCHROOM_VOICE_STRIP_OPENERS
+  })
+
+  it('does NOT strip a leading affirmation by default', () => {
+    const r = scrubVoice("You're absolutely right, the build is broken.")
+    expect(r.scrubbed).toBe("You're absolutely right, the build is broken.")
+    expect(r.openersStripped).toBe(0)
+  })
+
+  it('does NOT strip "Great catch" by default', () => {
+    const r = scrubVoice('Great catch! Fixed it.')
+    expect(r.scrubbed).toBe('Great catch! Fixed it.')
+    expect(r.openersStripped).toBe(0)
+  })
+
+  it('STILL normalizes em-dashes by default (punctuation, no content removed)', () => {
+    const r = scrubVoice('on it — checking the calendar')
+    expect(r.scrubbed).toBe('on it, checking the calendar')
+    expect(r.replaced).toBe(1)
+    expect(r.openersStripped).toBe(0)
+  })
+
+  it('an affirmation opener with an em-dash keeps the words, fixes only the dash', () => {
+    const r = scrubVoice('Exactly right — the token had expired.')
+    // Opener preserved; the em-dash after it becomes a comma.
+    expect(r.scrubbed).toBe('Exactly right, the token had expired.')
+    expect(r.openersStripped).toBe(0)
+    expect(r.replaced).toBe(1)
+  })
+})

package/telegram-plugin/text-voice-scrub.ts

@@ -12,22 +12,27 @@
  * owns enforcement, soft instructions fail under load. Make the
  * framework do it.
  *
- * Scope. Two mechanical transforms, both semantically safe:
- *   1. Em / en dashes -> comma/period/hyphen. Pure transform with no
- *      semantic loss on whitespace-separated prose; a no-op inside code
- *      or a URL.
+ * Scope. By default ONE mechanical transform, the only one that removes
+ * no content:
+ *   1. Em / en dashes -> comma/period/hyphen. Pure punctuation
+ *      substitution, no semantic loss on whitespace-separated prose; a
+ *      no-op inside code or a URL. Kept deterministic because prompt-only
+ *      guidance was measured to fail at it (em-dashes in 73% of replies
+ *      despite the SOUL rule).
+ *
+ * OPT-IN, off by default:
  *   2. Leading sycophancy openers ("You're absolutely right", "Great
- *      catch", "Exactly right") -> deleted, next word recapitalized. A
- *      leading pure-affirmation clause carries near-zero meaning, so
- *      removing it strips the AI-tell without touching the substance.
- *      Conservative by construction: only at the very start, only the
- *      known affirmation set, only when real content follows (a
- *      standalone "You're absolutely right!" ack is left intact).
+ *      catch") -> deleted + recapitalized. This one removes WORDS, and a
+ *      context-free hook can strip a sincere "good catch, that was my
+ *      bug" along with the hollow kind. Per operator steer (2026-06),
+ *      tone is carried by the prompt VOICE directive (where the model has
+ *      context to keep genuine acknowledgement and drop only the empty
+ *      reflexive praise), not by blind deletion here. Re-enable the
+ *      backstop with `SWITCHROOM_VOICE_STRIP_OPENERS=1`.
  *
- * Still scoped OUT: the wider mid-sentence "AI-tell phrase denylist"
+ * Always scoped OUT: the wider mid-sentence "AI-tell phrase denylist"
  * (smoking gun, delve, etc.). Substituting those mid-clause risks
- * semantic loss, so they stay with the prompt-side voice guidance
- * (the turn-pacing VOICE directive), not this mechanical gate.
+ * semantic loss, so they stay with the prompt-side voice guidance.
  *
  * Pipeline integration. Apply BEFORE markdownToHtml so the scrub
  * runs on the original model text, not on rendered HTML where
@@ -82,6 +87,25 @@ function enabled(): boolean {
   return !(v === '1' || v === 'true')
 }
 
+/**
+ * Leading-affirmation stripping is OPT-IN and OFF by default.
+ *
+ * Rationale (operator steer, 2026-06): tone should be carried by the
+ * prompt (the VOICE directive), where the model has context to keep a
+ * genuine acknowledgement and drop only the hollow reflexive kind.
+ * Deleting an opener in a context-free hook is bad UX: it can strip a
+ * sincere "good catch, that was my bug" along with the empty praise.
+ * So the deterministic layer no longer removes WORDS by default; it
+ * only normalizes em/en dashes (a punctuation substitution that removes
+ * no content, and that prompt-only guidance was measured to fail at).
+ * Set `SWITCHROOM_VOICE_STRIP_OPENERS=1` to re-enable the deterministic
+ * opener strip as a backstop.
+ */
+function openerStripEnabled(): boolean {
+  const v = process.env.SWITCHROOM_VOICE_STRIP_OPENERS
+  return v === '1' || v === 'true'
+}
+
 /**
  * Leading sycophancy/affirmation openers. Matched ONLY at the very start
  * of the message, ONLY this known pure-filler set, and the trailing
@@ -250,7 +274,13 @@ export function scrubVoice(text: string): VoiceScrubResult {
     return { scrubbed: text, replaced: 0, openersStripped: 0 }
   }
   const { parked, parts } = park(text)
-  const opener = stripLeadingAffirmation(parked)
+  // Opener strip is opt-in (default off) — see openerStripEnabled(). By
+  // default the deterministic layer removes no words; only em/en dashes
+  // are normalized below, and tone is left to the prompt's VOICE
+  // directive where the model can judge genuine vs hollow.
+  const opener = openerStripEnabled()
+    ? stripLeadingAffirmation(parked)
+    : { out: parked, count: 0 }
   const { out, replaced } = replaceDashes(opener.out)
   const total = replaced + opener.count
   if (total === 0) {

package/telegram-plugin/uat/scenarios/fuzz-voice-scrub-dm.test.ts

@@ -1,18 +1,20 @@
 /**
- * Voice-scrub fuzz — end-to-end proof of the deterministic voice gate.
+ * Voice-scrub fuzz — end-to-end check of the voice layers.
  *
- * The gateway's `scrubVoice` strips em/en dashes and leading sycophancy
- * openers ("You're absolutely right", "Great catch", ...) from every
- * outbound reply. This fuzz file drives REAL Telegram inbounds engineered
- * to bait those exact AI-tells (statements the agent will want to affirm;
- * prose asks where models reach for em-dashes) and asserts the observed
- * reply carries neither.
+ * Two layers with different strengths:
+ *   - Em/en dashes are DETERMINISTIC: the gateway's `scrubVoice`
+ *     normalizes every dash on every outbound reply, so "no em-dash
+ *     reaches the user" is a hard, observable guarantee (asserted).
+ *   - Sycophancy openers are PROBABILISTIC: the deterministic opener
+ *     strip is off by default (operator steer 2026-06: context-free word
+ *     deletion is bad UX), and tone is carried by the prompt VOICE
+ *     directive where the model can keep genuine acknowledgement. So an
+ *     opener is a soft signal (warn), not a gate failure.
  *
- * Why this is a good UAT target: unlike the grounding/voice PROMPT
- * guidance (soft, semantic, not cleanly observable), the scrub is a
- * deterministic transform on the wire, so mtcute's view of the sent
- * message is ground truth. If an em-dash or a leading affirmation reaches
- * the user, the gate failed.
+ * This fuzz file drives REAL Telegram inbounds engineered to bait both
+ * (statements the agent will want to affirm; prose asks where models
+ * reach for em-dashes). mtcute's view of the sent message is ground
+ * truth for the deterministic dash check.
  *
  * Self-skips green when the harness can't spin up (env unwired) — same as
  * the sibling fuzz files; uat/** is excluded from gating CI.
@@ -61,7 +63,7 @@ const LEADING_AFFIRMATION_RE =
 describe("uat: voice-scrub fuzz — no em-dashes, no sycophancy openers reach the user", () => {
   for (const vc of VOICE_CASES) {
     it(
-      `[voice] ${vc.name} — reply is dash-free and affirmation-free`,
+      `[voice] ${vc.name} — reply is dash-free (affirmation now prompt-tier)`,
       async () => {
         const sc = await spinUp({ agent: "test-harness" });
         try {
@@ -87,10 +89,15 @@ describe("uat: voice-scrub fuzz — no em-dashes, no sycophancy openers reach th
             );
           }
 
-          // Invariant 3: reply does not OPEN with a sycophancy affirmation.
+          // Invariant 3 (SOFT): reply ideally does not OPEN with a hollow
+          // affirmation. This is now PROBABILISTIC, not deterministic: the
+          // opener strip is off by default and tone is the prompt VOICE
+          // directive's job, so an occasional opener is a soft signal (the
+          // model judged it genuine), not a hard gate failure. Warn, don't
+          // fail — a hard assert here would flake on a prompt-driven lever.
           if (LEADING_AFFIRMATION_RE.test(text.trim())) {
-            throw new Error(
-              `[voice] ${vc.name}: reply opened with a stripped-class affirmation. `
+            console.warn(
+              `[voice] ${vc.name}: reply opened with an affirmation (prompt-tier, not enforced). `
               + `Reply: ${JSON.stringify(text.slice(0, 200))}`,
             );
           }