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]

Codex review: needs maintainer review before merge. Reviewed August 15, 2026, 2:47 AM ET / 06:47 UTC.

ClawSweeper review

What this changes

The PR adds an empty Unreleased section above the v0.17.1 changelog entry for the next release cycle.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open: this is the documented post-release closeout step, and current main still starts with the v0.17.1 section rather than an Unreleased heading. The two-line, bot-authored diff is correct and introduces no runtime or security concern. Likely related people: Peter Steinberger (high confidence).

Priority: P3
Reviewed head: 7c0dd8707091232f388423499b2e0ffb23f6969d

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	A focused, policy-aligned release-closeout patch with no correctness or security findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored release-closeout PR changes only release documentation; 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 bot-authored release-closeout PR changes only release documentation; runtime behavior proof is not applicable.
Evidence reviewed	5 items	Documented release contract: The release guide explicitly requires the published release to open the next patch's Unreleased closeout PR. Current-main state: Current main begins with the dated v0.17.1 section and does not yet contain an Unreleased heading, so the central change is not already implemented. Focused PR diff: The branch adds only the documented Unreleased heading and blank separator above v0.17.1.
Findings	None	None.
Security	None	None.

How this fits together

The release workflow publishes a verified version from main and then opens a follow-up changelog closeout PR. The Unreleased heading collects subsequent release notes while leaving shipped version entries below it.

flowchart LR
  A[Protected main release] --> B[Verified version published]
  B --> C[Release closeout PR]
  C --> D[Unreleased changelog section]
  D --> E[Next release notes]

Loading

Before merge

• Complete next step (P2) - This is a normal bot-authored release-closeout PR with no concrete repair-lane work required.

Agent review details

Security

None.

Review metrics

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

Technical review

Best possible solution:

Merge the focused closeout change so subsequent release notes have the documented Unreleased landing section.

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

Not applicable: this is a release-closeout documentation change, not a report of broken runtime behavior.

Is this the best way to solve the issue?

Yes: adding the heading is the exact lightweight handoff required by the repository's release guide after publishing a version.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 97e14efdf91a.

Labels

Label changes:

• add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.

Label justifications:

• P3: This is low-risk release-note housekeeping with no user-facing runtime change.
• 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 bot-authored release-closeout PR changes only release documentation; runtime behavior proof is not applicable.

Evidence

What I checked:

• Documented release contract: The release guide explicitly requires the published release to open the next patch's Unreleased closeout PR. (docs/release.md:16, 97e14efdf91a)
• Current-main state: Current main begins with the dated v0.17.1 section and does not yet contain an Unreleased heading, so the central change is not already implemented. (CHANGELOG.md:3, 97e14efdf91a)
• Focused PR diff: The branch adds only the documented Unreleased heading and blank separator above v0.17.1. (CHANGELOG.md:3, 7c0dd8707091)
• Release and ownership provenance: The current changelog and v0.17.1 release preparation were introduced by the tagged main commit, authored by Peter Steinberger; the tag check identifies v0.17.1. (CHANGELOG.md:1, 97e14efdf91a)
• Review continuity: The current head matches the two prior completed review cycles, both of which found no actionable patch findings. (7c0dd8707091)

Likely related people:

• Peter Steinberger: Authored the current tagged release-preparation commit that introduced the current changelog on main. (role: recent release and changelog contributor; confidence: high; commits: 97e14efdf91a; 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 (2 earlier review cycles)

• reviewed 2026-08-14T20:05:27.052Z sha 7c0dd87 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T04:56:52.737Z sha 7c0dd87 :: needs maintainer review before merge. :: none