v0.14.6 — Forward roadmap audit.

Candidate slice

The v0.14.6 cycle is single-slice. The work is docs-only and is the close-of-cycle pattern the v0.14.4 "Story Coverage" cycle established (PRs #198 + #200: CLAUDE.md invariants refresh + ROADMAP v0.3.0 historical audit).

• v0.14.5 doc-rotation closeout — the actual work. Updates 4 files: ROADMAP.md v0.14.5 cycle block (In Progress → Shipped with ✅ Done rows for PRs #222 / #223 / #224 / #225), this forward-roadmap doc (v0.14.4 + v0.14.5 entries closed out), the public frontend/roadmap/v0.14.5.html (planned → shipped + "What shipped" section + install link to the v0.14.5 release), and a new docs/v0.14.6_plan.md (the v0.14.6 cycle plan doc per the established docs/v0.14.x_plan.md convention).

Open questions

For the maintainer:

1. Is the v0.14.6 release cut a separate PR?

   Per CLAUDE.md golden rule #5 ("don't let the badge lie"), the README release badge reflects the most recent fully shipped release. A docs-only cycle still counts as shipped for the badge; the v0.14.6 release cut is therefore a separate Tier C PR (mirror of PR #225) that bumps the version surface to 0.14.6. Default: yes, the v0.14.6 release cut is a separate PR.

2. Should the v0.14.6 cycle also fix the release.yml landing-page step?

   The v0.14.5 release run (#30738207436) failed at the "Update beemuu.com landing page" step because the BEEMUU_VPS_SSH_KEY / BEEMUU_VPS_HOST secrets aren't configured in the repo. The v0.14.6 cycle could ship a release.yml change that makes the landing-page step best-effort + documents the secret-requirements in a new docs/ops/release-yml-secrets.md. Default: yes, ship the docs change in v0.14.6 alongside the audit PR.

Contribute

If you have a slice in mind, open a PR against main on the Beemuu repo. The maintainers will either merge it directly (Tier A) or roll it into the next cycle's plan doc.

FAQ