chore(main): release muzzle 0.2.1

[github-actions]

🤖 I have created a release beep boop

0.2.1 (2026-03-18)

Features

• actionable block messages + allow CLAUDE.md in worktrees (#18) (71a07bb)
• build: add deploy target to Makefile (7c0e986)
• initial session isolation system (9c78646)
• multi-workspace + XDG state directory separation (#22) (78637bb)
• OpenSSF Scorecard hardening + test coverage expansion (#16) (c804a25)
• structured logging, semver, fuzz, proptest, benchmarks, product docs (#4) (e1033cc)

Bug Fixes

• add catch_unwind to ensure-worktree binary (3db088b)
• add flock advisory lock to append_spec_entry (f11f92d)
• ci: badges, scorecard SARIF, release-please manifest (#11) (31c55f4)
• ci: remove broken GITHUB_TOKEN close+reopen from release-please (#17) (c72063f)
• pipe stdout in git commands and emit JSON from SessionStart (e141b88)
• resolve clippy, rustfmt, and flaky rate-limit test (ea04c70)
• stdout contamination + setup docs (813151c)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated release PR generated by Release Please, bumping muzzle from 0.2.0 to 0.2.1. The version is updated consistently across all four changed files (Cargo.toml, Cargo.lock, .release-please-manifest.json, and CHANGELOG.md), so the mechanical part of the release is correct.

The root cause of the CHANGELOG quality issues (duplicate entries and misplaced [Unreleased] section) has already been identified in earlier review threads: the muzzle-v0.2.0 git tag is absent, which causes release-please to walk back through the full commit history and re-capture commits that were already shipped in 0.2.0. Those issues are tracked in previous threads and do not need to be repeated here.

Key observations:

• Version bump 0.2.0 → 0.2.1 is consistent across all changed files.
• The comparison URL in the new CHANGELOG header (compare/muzzle-v0.2.0...muzzle-v0.2.1) will be a broken link until the muzzle-v0.2.0 tag is pushed retroactively (as suggested in the previous review thread).
• Cargo.lock and Cargo.toml changes are minimal and correct; no dependency versions were altered.
• The CHANGELOG.md structural issues (misplaced [Unreleased] block, duplicate entries) are pre-existing consequences of the missing release tag and are covered in prior review comments.

Confidence Score: 3/5

• Safe to merge for code correctness, but the CHANGELOG remains inaccurate until the missing muzzle-v0.2.0 git tag is created.
• The Rust source and manifest changes are trivially correct — only version strings are updated. The confidence deduction comes entirely from the CHANGELOG issues flagged in prior review threads: duplicate entries and the misplaced [Unreleased] section, both rooted in the absence of a muzzle-v0.2.0 git tag. Merging without fixing the tag means future release-please runs will continue to produce inaccurate changelogs.
• CHANGELOG.md — duplicate entries and misplaced [Unreleased] section due to missing muzzle-v0.2.0 git tag.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.2.0 to 0.2.1 — straightforward, consistent with Cargo.toml/Cargo.lock.
Cargo.toml	Package version bumped from 0.2.0 to 0.2.1; all other fields unchanged.
Cargo.lock	muzzle package version updated from 0.2.0 to 0.2.1 in the lockfile; all dependencies unchanged.
CHANGELOG.md	New 0.2.1 section added by release-please; [Unreleased] block is misplaced between 0.2.1 and 0.2.0 rather than at the top, and the comparison URL depends on a muzzle-v0.2.0 git tag that does not yet exist.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release-please bot detects new commits] --> B[Bump manifest 0.2.0 to 0.2.1]
    B --> C[Update Cargo.toml version = 0.2.1]
    B --> D[Update Cargo.lock muzzle 0.2.1]
    B --> E[Generate CHANGELOG.md 0.2.1 section]
    E --> F{muzzle-v0.2.0 tag exists?}
    F -- No --> G[Comparison URL broken]
    F -- No --> H[Commits without anchor cause duplicate entries]
    F -- Yes --> I[Clean diff and correct entries]
    E --> J{Unreleased block in CHANGELOG?}
    J -- Yes --> K[Inserted below 0.2.1 instead of at top]
    J -- No --> L[No misplacement issue]

Loading

_{Last reviewed commit: "chore(main): release..."}