switchroom 0.20.15 → 0.20.16

package/dist/cli/switchroom.js

@@ -2120,7 +2120,7 @@ var init_esm = __esm(() => {
 });
 
 // src/build-info.ts
-var VERSION = "0.20.15", COMMIT_SHA = "76c19936";
+var VERSION = "0.20.16", COMMIT_SHA = "fc0a754f";
 
 // src/cli/resolve-version.ts
 import { existsSync, readFileSync } from "node:fs";

package/dist/host-control/main.js

@@ -21559,7 +21559,7 @@ function allocateAgentUid(name) {
 }
 
 // src/build-info.ts
-var VERSION = "0.20.15";
+var VERSION = "0.20.16";
 
 // src/setup/hindsight-recall-passthrough.ts
 var HINDSIGHT_RECALL_TAG_WEIGHT_SEED = Object.freeze({ sidechain: 0.8 });

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.20.15",
+  "version": "0.20.16",
   "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": {
@@ -51,6 +51,7 @@
     "lint:litellm-config-guard": "node scripts/check-litellm-config-guard.mjs",
     "lint:release-asset-contract": "node scripts/check-release-asset-names.mjs",
     "lint:changelog-entry": "node scripts/check-changelog-entry.mjs",
+    "changelog:generate": "node scripts/gen-changelog-entry.mjs",
     "lint:agent-attribution-trailers": "node scripts/check-agent-attribution-trailers.mjs",
     "lint:hostd-template-guard": "bun scripts/check-hostd-template-guard.ts",
     "lint:bench-baseline-anonymised": "node scripts/check-bench-baseline-anonymised.mjs",

package/skills/dev-protocol/SKILL.md

@@ -139,6 +139,17 @@ is not a rebuttal.
   `AWAITING_CHECKS` means a required workflow is not listening for
   `merge_group`; `.github/MERGE-QUEUE.md` owns that failure mode and the
   invariants that prevent it.
+- **Stage the CHANGELOG entry author-side, before `gh pr create`.** A PR that
+  changes shippable code must add a `## Unreleased` entry (#4469's
+  `check-changelog-entry.mjs`, part of `npm run lint`, enforces it). Don't
+  hand-write it: run `bun run changelog:generate` in the repo — it derives the
+  entry from your conventional-commit title, appends it under `## Unreleased`
+  (idempotently — a second run is a no-op), and respects the escape hatches. Then
+  commit CHANGELOG.md so it lands in your own push. It runs AUTHOR-side, not in
+  CI, because a CI commit-back with the default `GITHUB_TOKEN` cannot re-trigger
+  the required checks and would wedge the PR (`.github/MERGE-QUEUE.md` §
+  "Author-side changelog generation"). Opt a docs/chore/test PR out with the
+  `no-changelog` label or a `[skip changelog]` token on its own line.
 - **A test that wouldn't fail on the bug it guards is not a test.** Assert the
   observable outcome, not that the code path executed.
 - **Prefer a deterministic mechanism over prompt discipline.** If a check, a

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

@@ -103439,10 +103439,10 @@ function startOutboxSweep(deps) {
 }
 
 // ../src/build-info.ts
-var VERSION2 = "0.20.15";
-var COMMIT_SHA = "76c19936";
-var COMMIT_DATE = "2026-08-07T10:03:58Z";
-var LATEST_PR = 4512;
+var VERSION2 = "0.20.16";
+var COMMIT_SHA = "fc0a754f";
+var COMMIT_DATE = "2026-08-07T22:36:16Z";
+var LATEST_PR = 4520;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts