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 21, 2026, 12:03 PM ET / 16:03 UTC.

ClawSweeper review

What this changes

The PR adds an empty Unreleased section above v0.17.1 in CHANGELOG.md for the next release cycle.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open: current main and v0.17.1 do not yet contain an Unreleased heading, while this focused bot-authored release-closeout PR adds exactly that missing next-cycle structure.

Priority: P3
Reviewed head: 7c0dd8707091232f388423499b2e0ffb23f6969d

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct release-closeout documentation patch with no functional findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored release-note-only change has no runtime behavior that requires contributor proof.
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 release-note-only change has no runtime behavior that requires contributor proof.
Evidence reviewed	4 items	Current main lacks the heading: The v0.17.1 entry immediately follows the changelog title on current main; no Unreleased section exists there. Focused proposed change: The PR adds only the two-line Unreleased heading above the v0.17.1 release entry. Release-note ownership history: Blame attributes the current v0.17.1 changelog header to the release-preparation commit by Peter Steinberger.
Findings	None	None.
Security	None	None.

How this fits together

wacli’s changelog records released versions and upcoming user-visible changes. Release closeout creates the latest version entry, and this heading provides the destination for notes accumulated before the next release.

flowchart LR
  A[Verified release] --> B[Release closeout]
  B --> C[Changelog]
  C --> D[Unreleased section]
  D --> E[Next release notes]

Loading

Before merge

• Complete next step (P2) - No repair-lane work is needed; this is a normal focused release-closeout PR awaiting routine merge review.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Merge the empty heading so subsequent release notes have one consistent place to accumulate.

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

Not applicable: this is a changelog-structure update, not a reported runtime defect.

Is this the best way to solve the issue?

Yes: adding the heading directly after the verified release is the narrowest maintainable way to open the next release-note cycle.

AGENTS.md: found and applied where relevant.

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

Labels

Label justifications:

• P3: This is a two-line release-note maintenance change with no runtime, data, or compatibility 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: This bot-authored release-note-only change has no runtime behavior that requires contributor proof.

Evidence

What I checked:

• Current main lacks the heading: The v0.17.1 entry immediately follows the changelog title on current main; no Unreleased section exists there. (CHANGELOG.md:3, 97e14efdf91a)
• Focused proposed change: The PR adds only the two-line Unreleased heading above the v0.17.1 release entry. (CHANGELOG.md:3, 7c0dd8707091)
• Release-note ownership history: Blame attributes the current v0.17.1 changelog header to the release-preparation commit by Peter Steinberger. (CHANGELOG.md:3, 97e14efdf91a)
• Release baseline: The current-main release-preparation commit is contained in the v0.17.1 tag, confirming this PR follows the verified release rather than duplicating an unreleased main change. (CHANGELOG.md:3, 97e14efdf91a)

Likely related people:

• Peter Steinberger: Authored the current v0.17.1 release-preparation commit and the changelog header immediately below this proposed section. (role: recent release-note contributor; confidence: high; commits: 97e14efdf91a; files: CHANGELOG.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-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
• reviewed 2026-08-15T06:47:23.476Z sha 7c0dd87 :: needs maintainer review before merge. :: none