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 22, 2026, 8:53 AM ET / 12:53 UTC (Revision 2).

ClawSweeper review

What this changes

Adds an empty Unreleased section above the published 0.13.1 changelog.

Merge readiness

✅ Ready for maintainer review

This PR remains useful: the pinned main revision lacks the next Unreleased section, and the change matches the documented release closeout process. No blocking defect was found.

Priority: P3
Reviewed head: 2156dce15905ce9ea4cf550e23ad811e6e866b67

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct housekeeping patch consistent with the documented release process.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only change has no runtime behavior to demonstrate; the complete diff establishes the intended document change.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This bot-authored changelog-only change has no runtime behavior to demonstrate; the complete diff establishes the intended document change.
Evidence reviewed	5 items	Complete introduced change: The pinned base-to-head diff adds only the Unreleased heading and a blank line; published release content is unchanged. Documented closeout requirement: The release checklist explicitly requires the closeout PR to open the next Unreleased changelog section. Still necessary on pinned main: The inspected main changelog begins with the dated 0.13.1 section and has no Unreleased heading. The supplied release context identifies v0.13.1 at this same revision.
Findings	None	None.
Security	None	None.

How this fits together

spogo’s changelog records published releases and pending changes. Release closeout opens a new section for changes destined for the next release.

flowchart LR
  A[Published release] --> B[Release closeout]
  B --> C[Empty Unreleased section]
  C --> D[Future change entries]
  D --> E[Next dated release notes]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep an empty Unreleased section ready for future changes while preserving all published release notes.

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

Not applicable: this PR performs release housekeeping rather than fixing a runtime bug.

Is this the best way to solve the issue?

Yes: inserting the empty heading is the smallest change that satisfies the repository’s documented closeout requirement.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning medium; reviewed against 1e683b92c5f4.

Labels

Label changes:

No label changes.

Label justifications:

• P3: This is a two-line release-documentation housekeeping change with no runtime effect.
• 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: This bot-authored changelog-only change has no runtime behavior to demonstrate; the complete diff establishes the intended document change.

Evidence

What I checked:

• Complete introduced change: The pinned base-to-head diff adds only the Unreleased heading and a blank line; published release content is unchanged. (CHANGELOG.md:3, 2156dce15905)
• Documented closeout requirement: The release checklist explicitly requires the closeout PR to open the next Unreleased changelog section. (docs/RELEASING.md:65, 2156dce15905)
• Still necessary on pinned main: The inspected main changelog begins with the dated 0.13.1 section and has no Unreleased heading. The supplied release context identifies v0.13.1 at this same revision. (CHANGELOG.md:3, 1e683b92c5f4)
• Release-area routing: Available changelog and release-guide history repeatedly identifies Peter Steinberger in release preparation and release documentation. Deeper blame and patch-history inspection encountered unavailable historical blobs; no source-line introduction claim is made. (CHANGELOG.md, 1e683b92c5f4)
• Review continuity and discussion: The supplied previous review covers the same head and contains no findings or published rank-up moves. The timeline records steipete reopening the PR; no substantive discussion requests a different implementation. (2156dce15905)

Likely related people:

• steipete: 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.

History

Review history (1 earlier review cycle)

• reviewed 2026-09-22T12:44:36.344Z sha 2156dce :: needs maintainer review before merge. :: none