[Birfy]

Mechanical release that folds the four changelog fragments now on main into ## [0.2.11] - 2026-10-27 and bumps the core to 0.2.11. Covered by the standing approval for mechanical release PRs.

Why

The user wants to try the Workflows page on their own instance; v0.2.10 was cut at 2026-10-27T00:49Z and therefore predates #1304 (#1272 step 3), which merged at 02:41Z. So this release carries it.

What changed (only the mechanical release files)

• CHANGELOG.md: changelog.mjs release 0.2.11 --date 2026-10-27 folded 4 fragments; [Unreleased] left empty. No hand edits.
• changelog.d/: the 4 folded fragments removed (1252-board-archive.changed.md, 1253-claim-cue.fixed.md, 1266-feishu-connector-row.changed.md, 1299-workflows.added.md), README.md untouched.
• core/package.json, core/package-lock.json: 0.2.10 → 0.2.11.
• patches/ds-bot/0007-version-and-tooling.patch: its three added version lines bumped by hand (no git binary on this box).

Since v0.2.10: 9 commits on main (base ae2e4615).

Ran at this tip (Node 22.23.3, fresh tarball of main ae2e4615)

• changelog.mjs check → 4 fragments well formed before the fold, 0 after; release 0.2.11 wrote the section.
• check-release-version.mjs 0.2.11 → exit 0; release-notes.mjs 0.2.11 renders the new section.
• Diff of this commit: 8 files — the four mechanical files modified plus 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), smoke, typecheck, actionlint — CI covers them at this tip. No tag or release is created by this PR.

Preflight (routine step 0, fact-source self-check): latest tag v0.2.10, core/package.json 0.2.10, 4 unfolded fragments → behind, so this beat releases. Test on main ae2e4615 is green (run 40439886391); no v0.2.11 release or tag exists.

Tip SHA: 65dbb6e

Written-by: Release