switchroom 0.19.47 → 0.20.0

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.47",
+  "version": "0.20.0",
   "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": {
@@ -24,9 +24,9 @@
     "build": "node scripts/build.mjs",
     "build:cli": "node scripts/build.mjs && bun build --compile --target=bun-linux-x64 --minify bin/switchroom.ts --outfile switchroom-linux-amd64",
     "pretest": "npm run build",
-    "test": "vitest run && bun test telegram-plugin/tests/agent-state-dir-preload.test.ts telegram-plugin/tests/catch-all-forwarded-history.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/cross-turn-card-gate.test.ts telegram-plugin/tests/emission-authority-open-gate.test.ts telegram-plugin/tests/emission-authority-ping-gate.test.ts telegram-plugin/tests/emission-authority-card-drain-gate.test.ts telegram-plugin/tests/per-topic-current-turn.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/ipc-server-query-pending-permission.test.ts telegram-plugin/tests/ipc-server-check-pre-approved.test.ts telegram-plugin/tests/rollout-narration-edit-socket.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/registry/subagents-bugs.test.ts telegram-plugin/tests/subagent-watcher-parent-turn-key.test.ts telegram-plugin/tests/subagent-nested-dispatch.test.ts telegram-plugin/tests/nested-worker-visibility-harness.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resume-inbound-builder.test.ts telegram-plugin/registry/api-registry.test.ts telegram-plugin/registry/turns-schema.test.ts telegram-plugin/tests/idle-footer-wiring.test.ts telegram-plugin/tests/subagent-tracker-hooks.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/status-query-telemetry.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts telegram-plugin/tests/skill-proposal-card.test.ts",
+    "test": "vitest run && bun test telegram-plugin/tests/agent-state-dir-preload.test.ts telegram-plugin/tests/catch-all-forwarded-history.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/boot-briefing-builder.test.ts telegram-plugin/tests/cross-turn-card-gate.test.ts telegram-plugin/tests/emission-authority-open-gate.test.ts telegram-plugin/tests/emission-authority-ping-gate.test.ts telegram-plugin/tests/emission-authority-card-drain-gate.test.ts telegram-plugin/tests/per-topic-current-turn.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/ipc-server-buzz-dedup.test.ts telegram-plugin/tests/ipc-server-query-pending-permission.test.ts telegram-plugin/tests/ipc-server-check-pre-approved.test.ts telegram-plugin/tests/rollout-narration-edit-socket.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/registry/subagents-bugs.test.ts telegram-plugin/tests/subagent-watcher-parent-turn-key.test.ts telegram-plugin/tests/subagent-nested-dispatch.test.ts telegram-plugin/tests/nested-worker-visibility-harness.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resume-inbound-builder.test.ts telegram-plugin/registry/api-registry.test.ts telegram-plugin/registry/turns-schema.test.ts telegram-plugin/tests/idle-footer-wiring.test.ts telegram-plugin/tests/subagent-tracker-hooks.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/status-query-telemetry.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts telegram-plugin/tests/skill-proposal-card.test.ts",
     "test:vitest": "vitest run",
-    "test:bun": "bun test telegram-plugin/tests/agent-state-dir-preload.test.ts telegram-plugin/tests/catch-all-forwarded-history.test.ts src/vault/grants.test.ts src/vault/grants-db.test.ts src/vault/write-grants.test.ts src/vault/broker/server-grants.test.ts src/vault/broker/server-write-grants.test.ts src/vault/broker/server-scope-persist.test.ts src/vault/broker/server-tokenless-scope.test.ts src/vault/broker/server-mint-grant-passphrase-attest.test.ts src/vault/broker/server-passphrase-attest.test.ts src/vault/broker/server-mint-grant-posture-attest.test.ts src/vault/broker/server-admin-only-keys.test.ts src/vault/broker/client-token.test.ts src/vault/broker/server-unlock.test.ts src/vault/broker/auto-unlock.test.ts src/vault/broker/drift-detection.test.ts tests/vault-broker-passphrase.test.ts src/cli/vault-get-broker.test.ts src/vault/resolver-via-broker.test.ts src/vault/broker/scope.test.ts src/vault/broker/server.test.ts src/litellm/provision-apply-e2e.test.ts src/drive/disconnect.test.ts src/drive/grants.test.ts src/drive/oauth.test.ts src/drive/onboarding.test.ts src/drive/reconciler.test.ts src/drive/vault-slots.test.ts src/drive/wrapper.test.ts src/vault/approvals/kernel.test.ts src/vault/approvals/approval-origin.test.ts src/vault/approvals/self-approval-bypass.test.ts src/vault/approvals/schema-idempotent.test.ts src/vault/broker/server-approvals.test.ts telegram-plugin/tests/boot-probes.test.ts telegram-plugin/tests/boot-version-string.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/cross-turn-card-gate.test.ts telegram-plugin/tests/emission-authority-open-gate.test.ts telegram-plugin/tests/emission-authority-ping-gate.test.ts telegram-plugin/tests/emission-authority-card-drain-gate.test.ts telegram-plugin/tests/per-topic-current-turn.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/ipc-server-query-pending-permission.test.ts telegram-plugin/tests/ipc-server-check-pre-approved.test.ts telegram-plugin/tests/rollout-narration-edit-socket.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/silent-reply-guard.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/registry/subagents-bugs.test.ts telegram-plugin/tests/subagent-watcher-parent-turn-key.test.ts telegram-plugin/tests/subagent-nested-dispatch.test.ts telegram-plugin/tests/nested-worker-visibility-harness.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resume-inbound-builder.test.ts telegram-plugin/tests/subagent-tracker-hooks.test.ts telegram-plugin/tests/resolve-calling-subagent.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/status-query-telemetry.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/tests/subagent-watcher-workflow-visibility.test.ts telegram-plugin/uat/load-env.test.ts telegram-plugin/uat/feed-matcher.test.ts telegram-plugin/uat/uat-driver.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts telegram-plugin/tests/skill-proposal-card.test.ts",
+    "test:bun": "bun test telegram-plugin/tests/agent-state-dir-preload.test.ts telegram-plugin/tests/catch-all-forwarded-history.test.ts src/vault/grants.test.ts src/vault/grants-db.test.ts src/vault/write-grants.test.ts src/vault/broker/server-grants.test.ts src/vault/broker/server-write-grants.test.ts src/vault/broker/server-scope-persist.test.ts src/vault/broker/server-tokenless-scope.test.ts src/vault/broker/server-mint-grant-passphrase-attest.test.ts src/vault/broker/server-passphrase-attest.test.ts src/vault/broker/server-mint-grant-posture-attest.test.ts src/vault/broker/server-admin-only-keys.test.ts src/vault/broker/client-token.test.ts src/vault/broker/server-unlock.test.ts src/vault/broker/auto-unlock.test.ts src/vault/broker/drift-detection.test.ts tests/vault-broker-passphrase.test.ts src/cli/vault-get-broker.test.ts src/vault/resolver-via-broker.test.ts src/vault/broker/scope.test.ts src/vault/broker/server.test.ts src/litellm/provision-apply-e2e.test.ts src/drive/disconnect.test.ts src/drive/grants.test.ts src/drive/oauth.test.ts src/drive/onboarding.test.ts src/drive/reconciler.test.ts src/drive/vault-slots.test.ts src/drive/wrapper.test.ts src/vault/approvals/kernel.test.ts src/vault/approvals/approval-origin.test.ts src/vault/approvals/self-approval-bypass.test.ts src/vault/approvals/schema-idempotent.test.ts src/vault/broker/server-approvals.test.ts telegram-plugin/tests/boot-probes.test.ts telegram-plugin/tests/boot-version-string.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/boot-briefing-builder.test.ts telegram-plugin/tests/cross-turn-card-gate.test.ts telegram-plugin/tests/emission-authority-open-gate.test.ts telegram-plugin/tests/emission-authority-ping-gate.test.ts telegram-plugin/tests/emission-authority-card-drain-gate.test.ts telegram-plugin/tests/per-topic-current-turn.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/ipc-server-buzz-dedup.test.ts telegram-plugin/tests/ipc-server-query-pending-permission.test.ts telegram-plugin/tests/ipc-server-check-pre-approved.test.ts telegram-plugin/tests/rollout-narration-edit-socket.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/silent-reply-guard.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/registry/subagents-bugs.test.ts telegram-plugin/tests/subagent-watcher-parent-turn-key.test.ts telegram-plugin/tests/subagent-nested-dispatch.test.ts telegram-plugin/tests/nested-worker-visibility-harness.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resume-inbound-builder.test.ts telegram-plugin/tests/subagent-tracker-hooks.test.ts telegram-plugin/tests/resolve-calling-subagent.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/status-query-telemetry.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/tests/subagent-watcher-workflow-visibility.test.ts telegram-plugin/uat/load-env.test.ts telegram-plugin/uat/feed-matcher.test.ts telegram-plugin/uat/uat-driver.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts telegram-plugin/tests/skill-proposal-card.test.ts",
     "test:watch": "vitest",
     "lint": "tsc --noEmit && node scripts/check-plugin-references.mjs && bash scripts/check-bot-api-wrapping.sh && node scripts/check-bun-test-imports.mjs && node scripts/check-test-runner-coverage.mjs && node scripts/check-bun-module-mock-scope.mjs && node scripts/check-no-pii-secrets.mjs && node scripts/check-vault-test-hermeticity.mjs && node scripts/check-auth-test-hermeticity.mjs && node scripts/check-agent-state-dir-hermeticity.mjs && node scripts/check-no-broadcast-delivery.mjs && node scripts/check-stale-tool-descriptions.mjs && node scripts/check-mcp-instructions-budget.mjs && node scripts/check-web-subscription-honest.mjs && node scripts/check-no-unpinned-npx-playwright.mjs && node scripts/check-gateway-line-ratchet.mjs && node scripts/check-retry-flood-hooks.mjs && node scripts/check-callback-ctx-wrapping.mjs && node scripts/check-status-pin-single-path.mjs && node scripts/check-litellm-config-guard.mjs && node scripts/check-release-asset-names.mjs && node scripts/check-agent-attribution-trailers.mjs && node scripts/check-hindsight-write-redaction.mjs && bun scripts/check-secret-pattern-parity.ts",
     "lint:tsc": "tsc --noEmit",
@@ -63,6 +63,7 @@
     "commander": "^13.1.0",
     "grammy": "^1.44",
     "handlebars": "^4.7.8",
+    "nostr-tools": "^2.24.1",
     "posthog-node": "^5.29.2",
     "yaml": "^2.7.0",
     "zod": "^3.24.0"

package/profiles/_base/start.sh.hbs

@@ -57,6 +57,48 @@ if [ "$SWITCHROOM_RUNTIME" = "docker" ] && [ -z "$SWITCHROOM_DOCKER_TMUX_INNER"
   # `claude` --continue path, not the gateway), so this needs its own hoist.
   export SWITCHROOM_BOOT_RESUME="{{#if bootResumeMode}}{{{bootResumeMode}}}{{else}}in-flight{{/if}}"
 
+  # Boot-briefing transport flag (session_continuity.briefing; default
+  # 'legacy'). When 'gateway', the gateway daemon assembles the fresh-session
+  # reorientation briefing at boot from the durable history.db and injects it
+  # as a spooled synthetic inbound (<channel source="boot_briefing">) instead
+  # of the handoff-briefing.sh --append-system-prompt path. MUST be exported
+  # here, before the gateway fork below (same env-fork landmine as
+  # SWITCHROOM_BOOT_RESUME). The gateway also needs the resume MODE to
+  # suppress the briefing when 'continue'/'auto' may replay the transcript —
+  # hoist that too (the inner-pass SWITCHROOM_RESUME_MODE assignment below
+  # renders the same template value, so the two can never disagree).
+  export SWITCHROOM_SESSION_BRIEFING="{{#if sessionBriefingMode}}{{{sessionBriefingMode}}}{{else}}legacy{{/if}}"
+  export SWITCHROOM_RESUME_MODE="{{#if resumeMode}}{{{resumeMode}}}{{else}}handoff{{/if}}"
+
+  # Force-fresh suppression signal for the gateway boot briefing. The gateway
+  # suppresses the briefing when this boot is a /reset·/new fresh start —
+  # re-feeding the just-reset conversation into the fresh session would defeat
+  # the reset. It MUST NOT rely on existsSync(.force-fresh-session) at its own
+  # module-eval time: this OUTER pass forks the gateway with `&` (below) then
+  # execs the inner tmux pass, whose CONTINUE_FLAG block `rm`s the marker (see
+  # ~line 1262). The fork and the `rm` race with no ordering, and under boot
+  # CPU contention the `rm` can win before the gateway bundle evaluates its
+  # briefing check — the marker vanishes and the reset session gets re-fed the
+  # conversation it just reset. Snapshot the marker into env HERE, before the
+  # fork, so the gateway reads a value fixed at fork time and immune to the
+  # later `rm`. The inner pass still consumes the marker for the claude
+  # --continue / session-mode logic; this only mirrors it for the fork race.
+  if [ -f "{{agentDir}}/.force-fresh-session" ]; then
+    export SWITCHROOM_FORCE_FRESH=1
+  fi
+
+  # Session-generation stamp for the gateway boot briefing (#4242). Set ONCE
+  # here, per real boot, before the gateway fork below. `_switchroom_supervise`
+  # respawns the gateway `bun` process in a `while` loop inside this same shell
+  # (it does NOT re-run start.sh), so every crash-respawn inherits this exact
+  # value, while the next real container boot re-derives a fresh one. The
+  # gateway persists it the first time it briefs and skips re-minting when the
+  # persisted stamp matches — that distinguishes "supervisor respawned me into
+  # a still-live Claude session" (skip) from "genuine new boot" (brief). The
+  # epoch second keeps it monotonic across boots; $$ (this outer pass's PID)
+  # plus ${RANDOM} guarantee uniqueness even for two boots within one second.
+  export SWITCHROOM_GATEWAY_BOOT_ID="$(date +%s)-$$-${RANDOM}"
+
   # Gateway-consumed env MUST be exported HERE, before the gateway fork
   # below. The gateway daemon reads channels.telegram.* knobs (and any
   # agent env) from process.env at startup — e.g. SWITCHROOM_TG_STREAM_
@@ -455,6 +497,34 @@ x-litellm-tags: agent:$SWITCHROOM_AGENT_NAME,profile:${SWITCHROOM_AGENT_PROFILE:
       bun /opt/switchroom/agent-scheduler/index.js &
   fi
 
+  # 3b) Buzz co-channel inbound sidecar (Phase 1, channels.buzz).
+  #     A supervised sibling that opens a WebSocket Nostr subscription to a
+  #     closed Buzz relay, NIP-42-authenticates, and injects allowlisted
+  #     messages onto the gateway socket as synthesized turns
+  #     (meta.source="buzz") — exactly like the cron sidecar above. INBOUND
+  #     ONLY in Phase 1; replies land on Telegram (the authoritative surface).
+  #
+  #     Default OFF and deterministic: the block is present for every agent
+  #     (start.sh stays byte-identical fleet-wide) but forks the sidecar ONLY
+  #     when BUZZ_ENABLED=1 is set in the container env. NOTE: nothing in this
+  #     branch sets BUZZ_ENABLED (or the other BUZZ_* vars) — projecting an
+  #     ENABLED channels.buzz block into container env is DEFERRED to the
+  #     deploy-wiring phase. Until then the env is unset for every agent and
+  #     this block is a no-op, so the channel is dark by construction. The
+  #     sidecar itself also fails closed if its env is incomplete, and fetches
+  #     the nsec in-process from the vault broker (never an env var, never
+  #     logged).
+  if [ "$BUZZ_ENABLED" = "1" ] \
+     && [ -f /opt/switchroom/buzz-gateway/index.js ] \
+     && command -v bun >/dev/null 2>&1; then
+    # --oneshot-ok: the sidecar exits 0 when the channel resolves not-live
+    # (e.g. mirror:off, or a not-live env). A clean exit 0 = "nothing to do",
+    # so DON'T respawn it every 60s (that is the documented churn pattern
+    # above). A non-zero crash while live still respawns.
+    _switchroom_supervise buzz-gateway /var/log/switchroom/buzz-gateway.log --oneshot-ok \
+      bun /opt/switchroom/buzz-gateway/index.js &
+  fi
+
 {{#if cronSessionEnabled}}
   # 4) cheap cron SESSION (Tier 1, reference/rfcs/cheap-cron-sessions.md §2.2).
   #    A SECOND interactive claude (no -p) dedicated to context:fresh cron
@@ -1353,7 +1423,14 @@ if [ "$_HANDOFF_STALE" = "1" ]; then
   # daily memory into a compact context brief. Requires python3 (stdlib
   # sqlite3) for the Telegram history section; other sections only need
   # curl + jq (both optional — each source degrades gracefully).
-  if [ "$SWITCHROOM_RESUME_MODE" = "handoff" ] && command -v handoff-briefing.sh >/dev/null 2>&1; then
+  #
+  # SKIPPED when session_continuity.briefing='gateway': the gateway daemon
+  # then owns the reorientation briefing (built from the durable history.db
+  # and injected as a spooled <channel source="boot_briefing"> inbound), so
+  # running the shell assembler here would double-inject the same recent
+  # conversation. The Stop-hook .handoff.md path below is left untouched in
+  # this stage of the migration.
+  if [ "$SWITCHROOM_RESUME_MODE" = "handoff" ] && [ "{{#if sessionBriefingMode}}{{{sessionBriefingMode}}}{{else}}legacy{{/if}}" != "gateway" ] && command -v handoff-briefing.sh >/dev/null 2>&1; then
     export AGENT_DIR="{{agentDir}}"
     timeout 5 handoff-briefing.sh 2>/dev/null || true
   fi

package/profiles/default/CLAUDE.md.hbs

@@ -50,7 +50,7 @@ Creating, updating, or refreshing a mental model is **operator-approved** — do
 ### Directives (replaces feedback rules)
 Hard rules the agent must follow during reflect — guardrails that are always applied.
 
-- `mcp__hindsight__create_directive(text)` — e.g., `create_directive("Always prefer TypeScript over JavaScript for this user's projects")`. When the user gives you a correction or "always do X" rule, create a directive instead of writing a feedback `.md` file.
+- `mcp__hindsight__create_directive(text)` — e.g., `create_directive("Always prefer TypeScript over JavaScript for this user's projects")`. When the user gives you a correction or "always do X" rule, create a directive instead of writing a feedback `.md` file. If the rule can be enforced deterministically — a settings.json hook, a permission rule, a skill/script edit, or a config change — prefer that (instead of, or in addition to, the directive) and say which you did; reserve directives for judgment rules code can't enforce.
 
 (Read-only inspection tools like `list_memories`, `list_mental_models`, `get_mental_model`, `list_directives` are available under the `mcp__hindsight__*` namespace if you ever need them, but you rarely should — Hindsight's own auto-recall surfaces what matters and the operator handles bank curation out-of-band. The mental-model WRITE tools — `create`/`update`/`refresh`/`delete_mental_model` — are gated: propose via `mcp__switchroom-telegram__mental_model_propose`, don't call them directly.)
 

package/skills/dev-protocol/SKILL.md

@@ -18,6 +18,32 @@ judgement criteria. This skill carries the parts that are *this fleet's
 specific opinion* — the ones you would get wrong by defaulting to generic
 good practice, because our answer differs from the obvious one.
 
+## 0. The design contract binds first (repos that declare one)
+
+Switchroom declares its design contract in `reference/` (`reference/README.md`
+is the map; the repo CLAUDE.md "Design contract" section binds it to every
+PR). When the repo you are changing carries one, the whole protocol below
+runs *inside* that contract:
+
+- **Before non-trivial work, place the change in the contract:** which of the
+  four outcomes it advances, and which job spec it satisfies —
+  `reference/product-spec.md` owns the job index; survey specs cheaply with
+  `head -7 reference/jobs/*.md`. A change that maps to no outcome and no job
+  is a scoping question, not a coding task.
+- **The ship gate is the verdict rule, not just CI green:** a change ships
+  only when it (a) advances one of the four outcomes, (b) satisfies its job
+  spec — proven by that job's outcome UAT, (c) passes all three principle
+  checks in `reference/principles.md` (docs / defaults / consistency; a "no"
+  is a redesign, not a ship-and-patch), and (d) crosses no invariant in
+  `reference/invariants.md`. Cite the job spec in the PR body.
+- **Design lives in `reference/`, not `docs/`.** A design decision worth
+  recording is an RFC or design record in `reference/rfcs/` (`serves:` a job
+  or `backs:` an invariant), never a new doc under `docs/`.
+
+This does not add ceremony to small changes: §1's fast path stands, and on a
+single-concern change the verdict check is a one-line sanity pass, not a
+report.
+
 ## 1. Is this a "larger" task? (decides whether you design-align first)
 
 Treat it as larger — design report before implementing — when ANY of these hold:
@@ -37,7 +63,10 @@ Design-aligning a one-liner is its own failure mode.
 
 The report states what exists today **with citations**, what will change, the
 chosen approach, the alternatives you rejected and why, and the PR staging
-plan. Get alignment before implementing.
+plan. In a contract-carrying repo (§0) it opens with the verdict-rule
+mapping: the outcome advanced, the job spec satisfied, and any principle
+check or invariant the design brushes against. Get alignment before
+implementing.
 
 Then red-team your own plan item by item. Each item gets a verdict —
 `SOUND`, `RISK`, or `WRONG` — backed by evidence you can point at (a file you

package/skills/switchroom-architecture/SKILL.md

@@ -59,3 +59,8 @@ Switchroom is a multi-agent orchestrator built on Claude Code. It manages multip
 - [cascade.md](cascade.md) — three-layer config cascade semantics
 - [sub-agents.md](sub-agents.md) — delegation patterns and model routing
 - [telegram.md](telegram.md) — enhanced Telegram plugin features
+
+**Why it's built this way** lives in the repo's `reference/` directory — the
+design contract (`reference/README.md` is the map: vision, principles,
+invariants, product spec, job specs, RFCs). For "why does switchroom do X"
+questions, that is the source of truth; `docs/` is usage/operation only.

package/skills/switchroom-cli/SKILL.md

@@ -290,7 +290,7 @@ config-plus-recreate operation with three known traps. **Follow the runbook:
 
 ## Telegram plugin reference — "what MCP tools", "how does reply work"
 
-The `switchroom-telegram` plugin is an enhanced fork of the official Telegram MCP plugin and is the default for all switchroom agents. It exposes **9 MCP tools** (all prefixed `mcp__switchroom-telegram__`):
+The `switchroom-telegram` plugin is an enhanced fork of the official Telegram MCP plugin and is the default for all switchroom agents. It exposes **20+ MCP tools** (all prefixed `mcp__switchroom-telegram__`; the authoritative list is the tool declarations in `telegram-plugin/bridge/bridge.ts`). The core messaging set:
 
 | Tool | Purpose |
 |---|---|

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

@@ -23121,12 +23121,12 @@ function classifyClaudeError(raw) {
   try {
     return classifyInner(raw);
   } catch {
-    return "unknown-4xx";
+    return "unknown-5xx";
   }
 }
 function classifyInner(raw) {
   if (raw == null)
-    return "unknown-4xx";
+    return "unknown-5xx";
   const obj = typeof raw === "object" ? raw : {};
   const errorType = extractString(obj, "error_type") ?? extractString(obj, "type") ?? extractString(getNestedObj(obj, "error"), "type") ?? "";
   const errorCode = extractString(obj, "code") ?? extractString(getNestedObj(obj, "error"), "code") ?? "";
@@ -23171,13 +23171,16 @@ ${message}`;
   if (errorType === "agent-restarted-unexpectedly" || errorCode === "agent-restarted-unexpectedly") {
     return "agent-restarted-unexpectedly";
   }
+  if ((status == null || status >= 500) && (errorType === "server_error" || errorCode === "server_error" || sdkCode === "server_error" || errorType === "api_error" || errorCode === "api_error" || sdkCode === "api_error")) {
+    return "transport-transient";
+  }
   if (status != null) {
     if (status >= 400 && status < 500)
       return "unknown-4xx";
     if (status >= 500 && status < 600)
       return "unknown-5xx";
   }
-  return "unknown-4xx";
+  return "unknown-5xx";
 }
 function extractString(obj, key) {
   const v = obj[key];
@@ -23708,7 +23711,7 @@ ${errStr}`) ? "rate-limited" : "quota-exhausted" : classifyClaudeError({ type: e
   const raw = embeddedError ?? obj;
   const kind = classifyClaudeError(embeddedError ?? obj);
   const detail = extractDetailMessage(embeddedError) ?? extractDetailMessage(obj) ?? String(type ?? "");
-  const transient = kind === "rate-limited";
+  const transient = kind === "rate-limited" || kind === "transport-transient";
   const retry = extractRetryState(obj);
   const terminal = !transient ? true : retry.retryAttempt != null && retry.maxRetries != null ? retry.retryAttempt >= retry.maxRetries : isErrorLine;
   return { kind, raw, detail, transient, terminal };