chore(release): 0.11.0

[pbean]

What

Cuts release 0.11.0 — version stamped everywhere, ## [Unreleased] promoted to
## [0.11.0] — 2026-08-19 with a fresh empty Unreleased reopened above it, assets
regenerated, all on release/0.11.0.

Why 0.11.0, not 0.10.1

The release was requested as a patch. The section's contents are a minor.

"Has an ### Added section" is not the discriminator — 0.7.12 and 0.8.1 were both
patch releases carrying Added/Changed. What forces a minor here are two
compatibility breaks, and this CHANGELOG's own preamble says pre-1.0 breaking changes
land in a minor:

• psmux support floor → 3.3.8 (psmux 3.3.8 adoption: bump the floor to (3,3,7) and drop the retired workarounds #658). available() refuses 3.3.7 and below, so on
  such a host the backend reports unavailable and selection falls through entirely.
• post_dev_verify now fires on the repair leg (Expose structured verification command results to post_dev_verify plugins #641). In the entry's own words,
  handlers that assumed one call per story "must be idempotent."

Additive schema fields are deliberately not counted toward that: #501's
sweeps_refused and #294's adapter.binary-unrunnable are both additive, and their
entries argue STATUS_SCHEMA_VERSION / VALIDATE_SCHEMA_VERSION stay unchanged.

How

• release.py prepare 0.11.0 — stamped via sync_version.py (+ uv lock), reseeded the
  gitignored skill forks, regenerated screenshots + demo, ran trunk fmt, committed.
• Assets regenerated because src/bmad_loop/tui changed since v0.10.0 (the TUI modal dialogs: responsive widths + compact small-height layout #281 modal
  clamping and compact-layout work). Baseline is sound this time: v0.10.0 is the newest
  tag and an ancestor of main, so tui_changed_since() is not comparing across a
  divergent line the way chore(release): 0.10.0 #589 had to note.
• The section was promoted by renaming the existing heading, not by authoring a new
  one beside it; prepare inserted [0.11.0]: and re-pointed [Unreleased]: at
  compare/v0.11.0...HEAD.

Curation was minimal — the per-PR entries were already in house shape, so no entries
were merged, reworded, or dropped. Two edits only:

• added the missing (#595) citation to the ENAMETOOLONG entry — the sole gap found by
  a full commit-vs-CHANGELOG issue-ref sweep across all 215 commits since v0.10.0;
• rewrapped two lines that overran the section's ~100-col house wrap (126 and 113 cols).
  proseWrap: preserve means trunk fmt would never have caught these.

One deliberate omission. The verify/ redirect/FIFO hardening commits (9533ab63,
f722d8a5, 0dc29283) get no Fixed entries. Their commit messages establish the hazard
is reachable only because this same release first made verify/ something a session can
plant — every other category root and run-dir entry is engine-created — so no released
version was affected and nothing regressed for a 0.10.0 user.

Testing

release.py check — the same command CI's version-sync job runs — is green on all four
assertions: every version field agrees on 0.11.0, the root module.yaml mirror matches,
the ## [0.11.0] section is present, and [Unreleased]: compares against v0.11.0.
trunk check --no-fix (no filter) is clean on all 15 modified files. Working tree clean.

Changelog

n/a — this PR is the changelog promotion. No new entry is added; ## [Unreleased] is
reopened empty, which is what prepare and check both require.

Summary by CodeRabbit

• Release
  • Updated the BMAD Loop version to 0.11.0 across the package and plugin metadata.
  • Added the 0.11.0 changelog, including clarifications for verification-stream write failures, binary resolution, and atomic writes with filesystem-length limits.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ba1f8f94-5602-4437-bd4d-68755d4d0fdb

📥 Commits

Reviewing files that changed from the base of the PR and between 8c6f720 and 3e8f1e2.

⛔ Files ignored due to path filters (9)

• docs/images/dashboard.png is excluded by !**/*.png
• docs/images/dashboard.svg is excluded by !**/*.svg
• docs/images/demo.gif is excluded by !**/*.gif
• docs/images/settings.svg is excluded by !**/*.svg
• docs/images/start-run-modal.png is excluded by !**/*.png
• docs/images/start-run-modal.svg is excluded by !**/*.svg
• docs/images/sweep-decision.png is excluded by !**/*.png
• docs/images/sweep-decision.svg is excluded by !**/*.svg
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• .claude-plugin/marketplace.json
• CHANGELOG.md
• module.yaml
• pyproject.toml
• src/bmad_loop/__init__.py
• src/bmad_loop/data/skills/bmad-loop-setup/assets/module.yaml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The release metadata now uses version 0.11.0 across the plugin, module, project, and package. The changelog adds the release heading, clarifies several entries, and updates comparison links.

Changes

0.11.0 release alignment

Layer / File(s)	Summary
Version alignment and release notes .claude-plugin/marketplace.json, module.yaml, pyproject.toml, src/bmad_loop/__init__.py, src/bmad_loop/data/skills/bmad-loop-setup/assets/module.yaml, CHANGELOG.md	All version declarations now use 0.11.0. The changelog adds the release date, clarifies verification capture failures, binary resolution, and atomic-write limits, and updates release links.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 3e8f1

This release PR updates version metadata, promotes the changelog, and regenerates documented assets; the supplied checks are green and no actionable merge-blocking risk remains.

Poem

I’m a rabbit with a release note bright,
Version 0.11.0 hops into sight.
Metadata aligned in a tidy row,
Changelog details now clearly show.
Thump, thump—ship it just right!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the 0.11.0 release version update and matches the primary changes in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.11.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}