docs(changelog): open 0.13.1 after the 0.13.0 release

[steipete]

Post-release closeout: 0.13.0 is published on npm, GitHub, and Homebrew, so this opens the next Unreleased section per the release checklist.

🤖 Generated with Claude Code

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 5, 2026, 7:21 AM ET / 11:21 UTC.

ClawSweeper review

What this changes

Adds an empty 0.13.1 Unreleased section above the published 0.13.0 changelog entry.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open for maintainer review: this collaborator PR is a focused, correct release-closeout change that current main does not yet contain, with downstream publication confirmation remaining the merge prerequisite.

Priority: P3
Reviewed head: c48cfcd7188fbf486d24e938d83575c4d1469895

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	A clean, narrowly scoped documentation change that matches the documented release-closeout sequence.
Proof confidence	🌊 off-meta tidepool	Not applicable: This PR changes only CHANGELOG.md, so real runtime behavior proof is not applicable.
Patch quality	🦞 diamond lobster (5/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This PR changes only CHANGELOG.md, so real runtime behavior proof is not applicable.
Evidence reviewed	4 items	Documented closeout sequence: The release checklist explicitly directs maintainers to add the next patch Unreleased changelog stub after downstream verification and closeout. Current main still needs the section: Current main begins with the released 0.13.0 entry; the PR adds only the missing 0.13.1 Unreleased heading. Release and changelog provenance: The current changelog’s 0.13.0 entry is attributed to the tagged release commit, and that commit is contained by v0.13.0.
Findings	None	None.
Security	None	None.

How this fits together

Release closeout updates the changelog after a version is published and downstream package distribution is verified. The new Unreleased section is where notes for the next patch release will accumulate.

flowchart LR
A[Published 0.13.0] --> B[Downstream verification]
B --> C[Release closeout]
C --> D[Changelog]
D --> E[0.13.1 Unreleased section]

Loading

Before merge

• Resolve merge risk (P1) - The release checklist requires GitHub, npm, Homebrew, and downstream smoke verification before opening the next Unreleased section; CI cannot establish that external closeout condition.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog delta	1 file changed; 2 added, 0 removed	The patch is limited to the release-closeout heading and does not alter runtime behavior.

Merge-risk options

Maintainer options:

1. Confirm release closeout first (recommended)
   Keep this branch open until a maintainer verifies the required GitHub, npm, Homebrew, and downstream smoke closeout for 0.13.0.
2. Merge on the recorded release statement
   A maintainer may merge based on the PR’s stated publication confirmation and accept responsibility for any unverified downstream step.

Technical review

Best possible solution:

Merge the focused changelog update once a maintainer confirms the downstream 0.13.0 closeout asserted in the PR body is complete.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a changelog-only release-closeout update, not a reported runtime defect.

Is this the best way to solve the issue?

Yes, conditionally: the release checklist explicitly prescribes this exact stub after downstream verification, so the remaining question is confirmation of that prerequisite rather than a different implementation path.

AGENTS.md: found, but no applicable review policy affected this item.

Codex review notes: model internal, reasoning high; reviewed against 58986a78d0ee.

Labels

Label justifications:

• P3: This is a small, non-runtime release documentation update.
• merge-risk: 🚨 other: Its correctness depends on externally completed release-closeout steps that the source diff and CI do not prove.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This PR changes only CHANGELOG.md, so real runtime behavior proof is not applicable.

Evidence

What I checked:

• Documented closeout sequence: The release checklist explicitly directs maintainers to add the next patch Unreleased changelog stub after downstream verification and closeout. (docs/RELEASE.md:105, 58986a78d0ee)
• Current main still needs the section: Current main begins with the released 0.13.0 entry; the PR adds only the missing 0.13.1 Unreleased heading. (CHANGELOG.md:3, c48cfcd7188f)
• Release and changelog provenance: The current changelog’s 0.13.0 entry is attributed to the tagged release commit, and that commit is contained by v0.13.0. (CHANGELOG.md:3, 49dcd3e7fffd)
• Narrow reviewed diff: The branch changes one documentation file with two added lines and no deletions. (CHANGELOG.md:3, c48cfcd7188f)

Likely related people:

• Peter Steinberger: Current changelog lines and the v0.13.0 tagged release commit are attributed to Peter Steinberger; the proposed closeout follows that release workflow. (role: recent release and changelog contributor; confidence: high; commits: 49dcd3e7fffd; files: CHANGELOG.md, docs/RELEASE.md)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (3 earlier review cycles)

• reviewed 2026-08-04T22:12:52.552Z sha c48cfcd :: needs maintainer review before merge. :: none
• reviewed 2026-08-05T05:44:35.659Z sha c48cfcd :: needs maintainer review before merge. :: none
• reviewed 2026-08-05T09:34:04.211Z sha c48cfcd :: needs maintainer review before merge. :: none