switchroom 0.21.11 → 0.21.12

package/dist/cli/switchroom.js

@@ -2120,7 +2120,7 @@ var init_esm = __esm(() => {
 });
 
 // src/build-info.ts
-var VERSION = "0.21.11", COMMIT_SHA = "7a80af9d", COMMIT_DATE = "2026-08-14T09:19:49Z";
+var VERSION = "0.21.12", COMMIT_SHA = "66041822", COMMIT_DATE = "2026-08-14T20:57:00Z";
 
 // src/cli/resolve-version.ts
 import { existsSync, readFileSync } from "node:fs";

package/dist/host-control/main.js

@@ -21565,7 +21565,7 @@ function allocateAgentUid(name) {
 }
 
 // src/build-info.ts
-var VERSION = "0.21.11";
+var VERSION = "0.21.12";
 
 // 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.21.11",
+  "version": "0.21.12",
   "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": {
@@ -57,6 +57,7 @@
     "lint:claude-cli-lockstep": "node scripts/check-claude-cli-lockstep.mjs",
     "lint:changelog-entry": "node scripts/check-changelog-entry.mjs",
     "changelog:generate": "node scripts/gen-changelog-entry.mjs",
+    "changelog:cut": "node scripts/cut-changelog-release.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",
@@ -83,6 +84,7 @@
     "@types/bun": "^1.3.11",
     "@types/node": "^22.0.0",
     "@vitest/coverage-v8": "3.2.4",
+    "commonmark": "0.31.2",
     "typescript": "^5.7.0",
     "vitest": "^3.2.4"
   },

package/skills/dev-protocol/SKILL.md

@@ -139,17 +139,21 @@ 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
+- **Stage the changelog note author-side, before `gh pr create`.** A PR that
+  changes shippable code must add a NEW `changelog.d/` fragment file (#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.
+  hand-edit `CHANGELOG.md`: run `bun run changelog:generate` in the repo — it
+  derives a per-PR fragment (`changelog.d/<pr>-<slug>.<type>.md`) from your
+  conventional-commit title (idempotently — a second run is a no-op) and
+  respects the escape hatches. Then commit the fragment so it lands in your
+  own push. Fragment files are per-PR, so they never conflict with another
+  in-flight PR — editing the shared `## Unreleased` section does, which is
+  exactly the conflict class fragments replace (see `changelog.d/README.md`).
+  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/skills/switchroom-release/SKILL.md

@@ -22,14 +22,20 @@ Cut a release of `switchroom/switchroom` and get it live on the fleet. This is a
 1. `git fetch origin`, confirm `main` is at the commit you want released.
 2. `gh pr list --state open` — confirm no PR meant for this release is still open. Ask the operator if unsure.
 3. Confirm CI on `main` is green (`gh run list --branch main --limit 3`).
-4. Read `CHANGELOG.md` — the `## Unreleased` section is the **continuously-maintained** staging area for this release's notes. Every PR since the last release stages its own entry there as it merges, enforced by `scripts/check-changelog-entry.mjs` (part of `npm run lint`), so by release time this section should already read as a near-complete draft — you tidy and summarise, you do NOT author it from scratch. **An empty (or missing) `## Unreleased` at release time is now an ANOMALY, not the normal state:** it means either there genuinely is nothing to release, OR the enforcement was bypassed (`no-changelog` labels / `[skip changelog]` tokens on their own line on PRs that should have staged entries). Before assuming the former, cross-check against `git log <last-tag>..origin/main` — if real shippable work landed but Unreleased is bare, investigate and reconstruct rather than shipping a hollow release (this is exactly the v0.20.12 failure mode the enforcement exists to prevent).
+4. Read the staged notes — they live in TWO places, both **continuously maintained** as PRs merge and both enforced by `scripts/check-changelog-entry.mjs` (part of `npm run lint`): the `changelog.d/` **fragment files** (the primary path — every shippable PR adds its own `<pr>-<slug>.<type>.md`; see `changelog.d/README.md`) and any legacy/hand-staged entries under `## Unreleased` in `CHANGELOG.md`. Together they should already read as a near-complete draft — you assemble and tidy, you do NOT author from scratch. **Nothing staged at release time (no fragments AND an empty `## Unreleased`) is an ANOMALY, not the normal state** — `bun run changelog:cut` refuses to cut it: it means either there genuinely is nothing to release, OR the enforcement was bypassed (`no-changelog` labels / `[skip changelog]` tokens on their own line on PRs that should have staged notes). Before assuming the former, cross-check against `git log <last-tag>..origin/main` — if real shippable work landed but nothing is staged, investigate and reconstruct rather than shipping a hollow release (this is exactly the v0.20.12 failure mode the enforcement exists to prevent).
 5. Pick the next version: read the latest tag (`git tag --list 'v*' --sort=-v:refname | head -1`) and bump the patch (or minor if the operator asks). Confirm with the operator which.
 
-## Step 1 — Consolidate the changelog (the release commit is CHANGELOG-only)
+## Step 1 — Assemble the changelog (the release commit is CHANGELOG + fragment deletions only)
 
-- The section is maintained continuously (see pre-flight 4), so this step is now a **rename + tidy**, not authorship: change the `## Unreleased` header to `## vX.Y.Z — <one-line summary>`, then read through the staged entries and lightly edit for grouping/summary. If Unreleased was empty or thin, STOP and resolve the anomaly (pre-flight 4) before proceeding — do not invent a release note.
-- **Re-seed a fresh empty `## Unreleased` block at the top** (header + the convention HTML comment) immediately below `# Changelog`, so the staging area exists for the next cycle and `scripts/check-changelog-entry.mjs` keeps enforcing it. (Copy the comment block from the section you just renamed.)
-- The release commit touches **CHANGELOG.md only**. Do NOT bump `package.json` (placeholder discipline).
+- The notes are staged continuously (see pre-flight 4), so this step is **one command + a review**, not authorship:
+
+  ```bash
+  bun run changelog:cut -- --version vX.Y.Z --summary "<one-line summary>"
+  ```
+
+  `scripts/cut-changelog-release.mjs` folds every `changelog.d/` fragment (plus anything hand-staged under `## Unreleased`) into a new `## vX.Y.Z — <summary>` section grouped by category, **re-seeds a fresh empty `## Unreleased` block** (header + convention comment) below `# Changelog`, and **deletes the consumed fragment files**. Use `--dry-run` first to preview the assembled section. It FAILS LOUDLY on a double cut or an empty cut — if it refuses for "nothing to release", STOP and resolve the anomaly (pre-flight 4); do not invent a release note.
+- Read through the assembled section and lightly edit for grouping/summary before committing.
+- The release commit touches **CHANGELOG.md and the deleted `changelog.d/` fragments only**. Do NOT bump `package.json` (placeholder discipline). (A CHANGELOG + fragment-deletion PR changes no shippable code, so `check-changelog-entry.mjs` passes it without a staged note of its own — deleting fragments never counts as staging one.)
 - Branch protection blocks direct push to `main`, so: create a `release/vX.Y.Z` branch, push it, open a `chore: release vX.Y.Z` PR (base `main`), arm auto-merge (squash, delete-branch) on green CI.
 
 ## Step 2 — Create the DRAFT release on a PINNED SHA, then push the tag

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

@@ -105739,10 +105739,10 @@ function startOutboxSweep(deps) {
 }
 
 // ../src/build-info.ts
-var VERSION2 = "0.21.11";
-var COMMIT_SHA = "7a80af9d";
-var COMMIT_DATE = "2026-08-14T09:19:49Z";
-var LATEST_PR = 4713;
+var VERSION2 = "0.21.12";
+var COMMIT_SHA = "66041822";
+var COMMIT_DATE = "2026-08-14T20:57:00Z";
+var LATEST_PR = 4717;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts