chore: open next Unreleased section

[github-actions]

Opens the next Unreleased changelog section after the verified release.

Created by the fleet release closeout stage.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 28, 2026, 8:00 AM ET / 12:00 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased section above the v0.13.0 notes so future changes have a place in the changelog.

Merge readiness

✅ Ready for maintainer review

The v0.13.0 release and current main changelog have no next Unreleased section. This small PR supplies that still-needed heading, and no actionable defect was found.

Priority: P3
Reviewed head: 121a3af90ba9bb4893eab90b9da4465d627bf4af

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The narrow, correct changelog edit is supported by the release and main snapshots; runtime proof is inapplicable.
Proof confidence	🌊 off-meta tidepool	Not applicable: The bot-authored PR changes a changelog heading, whose placement is directly visible in the reviewed file; no stored-data contract changes.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The bot-authored PR changes a changelog heading, whose placement is directly visible in the reviewed file; no stored-data contract changes.
Evidence reviewed	6 items	Introduced change: The pinned PR delta adds only an Unreleased heading and a blank line above v0.13.0. Current main remains without the heading: The pinned main version begins with the v0.13.0 section, so it has not already implemented this change. Release boundary: The published v0.13.0 tag points at the pinned main commit; its changelog also lacks the next Unreleased heading.
Findings	None	None.
Security	None	None.

How this fits together

Gitcrawl's changelog records changes for each release. The release workflow includes that file in release archives, and the new heading gives upcoming notes a section before the next version is prepared.

flowchart LR
  A[Verified release] --> B[Versioned changelog notes]
  B --> C[Open Unreleased section]
  C --> D[Upcoming change notes]
  D --> E[Next release notes]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Land the heading after the verified v0.13.0 release so upcoming entries accumulate under one Unreleased section.

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

Not applicable: this is changelog housekeeping, and the pinned main and release-tag files directly establish the missing heading.

Is this the best way to solve the issue?

Yes. Adding the heading above the latest released version follows the prior changelog pattern with a two-line change.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning medium; reviewed against 58e5d6299e36.

Labels

Label changes:

• add P3: This is a small changelog housekeeping change with no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The bot-authored PR changes a changelog heading, whose placement is directly visible in the reviewed file; no stored-data contract changes.

Label justifications:

• P3: This is a small changelog housekeeping change with no runtime behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The bot-authored PR changes a changelog heading, whose placement is directly visible in the reviewed file; no stored-data contract changes.

Evidence

What I checked:

• Introduced change: The pinned PR delta adds only an Unreleased heading and a blank line above v0.13.0. (CHANGELOG.md:3, 121a3af90ba9)
• Current main remains without the heading: The pinned main version begins with the v0.13.0 section, so it has not already implemented this change. (CHANGELOG.md:3, 58e5d6299e36)
• Release boundary: The published v0.13.0 tag points at the pinned main commit; its changelog also lacks the next Unreleased heading. (CHANGELOG.md:3, 58e5d6299e36)
• Release workflow context: The release workflow includes CHANGELOG.md in the archive files. (.github/workflows/release-unified.yml:27, 58e5d6299e36)
• Relevant area history: Recent changelog history includes v0.13.0 release notes by Peter Steinberger and an earlier post-release Unreleased heading by github-actions[bot]. This identifies routing candidates, not source-line introduction. (CHANGELOG.md:5, 58e5d6299e36)
• Live PR state: The PR is open, unmerged, and points at the reviewed head and base.

Likely related people:

• Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• github-actions[bot]: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

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.