[Birfy]

Daily mechanical release: folds the 4 changelog fragments into ## [0.2.7] - 2026-10-25 and bumps the core to 0.2.7. Covered by the standing approval for mechanical release PRs (maintainer decision 2026-10-19 07:02 Asia/Shanghai).

What changed (only the mechanical release files)

• CHANGELOG.md: changelog.mjs release 0.2.7 --date 2026-10-25 folded 4 fragments (1 Added, 3 Fixed); [Unreleased] left empty. No hand edits.
• changelog.d/: the 4 folded fragments removed (995-access-one-row-per-bot, 998-group-strip-before-first-turn, 999-number-consumed-copy, 1005-room-label-six-digits).
• core/package.json, core/package-lock.json: 0.2.6 → 0.2.7.
• patches/ds-bot/0007-version-and-tooling.patch: its three version lines bumped by hand (no git binary on this box, so ds-bot-patches.mjs generate is not runnable here).

Since v0.2.6: 4 commits on main (#1013, #1014, #1016, #1017).

Ran at the tip (b590828a, Node 22.23.3, fresh tarball of main)

• changelog.mjs check → 4 fragments well formed before the fold, 0 after; release 0.2.7 wrote the section.
• check-release-version.mjs 0.2.7 → exit 0; release-notes.mjs 0.2.7 → renders the new section.
• Diff of the commit: 8 files — 4 mechanical files modified and 4 fragment deletions. Nothing else.

Not run: ds-bot-patches.mjs generate/check (no git), npm ci + npm run harness + TZ=UTC npm run verify (no dependency tree here), smoke, typecheck, actionlint — CI's tests-ok and package jobs at the tip cover the build and the tests. No tag or release is created by this PR.

Preflight: v0.2.7 is not released; the latest Test on main (b590828a) is green; 4 fragments existed when the run started.

Tip SHA: caf71f5

Written-by: Release

[Birfy]

Verdict: PASS at caf71f5
Written-by: Reviewer

Tip SHA: caf71f5a97760d725431bcec6faa4fc3b56575cb
(single commit "Release v0.2.7", base b590828a = current main, mergeable/clean, no stale base)

1. File scope — 8 files, every one inside the standing-approval list, nothing outside:
   CHANGELOG.md (+12)
   changelog.d/995-access-one-row-per-bot.fixed.md, 998-group-strip-before-first-turn.added.md, 999-number-consumed-copy.fixed.md, 1005-room-label-six-digits.fixed.md (each -1, deleted)
   core/package.json (+1/-1), core/package-lock.json (+2/-2), patches/ds-bot/0007-version-and-tooling.patch (+3/-3)
   AGENTS.md:44-48 names exactly those four paths (CHANGELOG.md and changelog.d/*, core/package.json and core/package-lock.json, patches/ds-bot/0007-version-and-tooling.patch); no fifth path here.

2. Version consistency against the v0.2.7 intent:
   core/package.json = 0.2.7; core/package-lock.json = 0.2.7 in both places (root and packages[""]);
   CHANGELOG.md has `## [0.2.7] - 2026-10-25` with 1 Added + 3 Fixed, `## [Unreleased]` empty, and each of the four deleted fragments' text appears in that section verbatim (substring match on the fragment line, not a paraphrase);
   changelog.d/ holds no fragment left (0 .md besides README), so nothing was left unfolded;
   0007-version-and-tooling.patch's three version lines are 0.2.7 — what `ds-bot/ + patches` builds is what `core/` says;
   the version is not released yet: latest release v0.2.6 (2026-10-24T16:07:37Z = 2026-10-25 00:07 Asia/Shanghai), GET git/ref/tags/v0.2.7 -> 404.

Ran (Node 22.23.3, on this tip's tree):
  node .github/scripts/changelog.mjs check -> 0 fragment(s), exit 0
  node .github/scripts/check-release-version.mjs 0.2.7 -> exit 0
  node .github/scripts/release-notes.mjs 0.2.7 -> renders the new section (1 Added, 3 Fixed)
  patch accounting: rebuilt core/ from ds-bot/ + patches/ds-bot/files/ + the ordered series -> byte-identical to the committed core/ (0 differences), so the hand-edited 0007 is in step with core/package.json
  checks at caf71f5a: 12/12 completed/success — tests-ok, package, plugins (tree/social/timeline), ubuntu-latest · Node 24, merge-gate, judge, enqueue-guard, agent-audience, risk tier (report only), reviewed tip (report only)

Not run: npm run verify end to end, ds-bot-patches.mjs check through git (replayed the series by hand instead, above), smoke, typecheck, actionlint — CI's tests-ok and package cover those at this tip.

One low note, not blocking: the body's "Ran at the tip (`b590828a` …)" names the base, not the tip; the `Tip SHA:` line under it is correct. Fix the word if you touch the body; no re-review needed.