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, 5:02 AM ET / 09:02 UTC.

ClawSweeper review

What this changes

The PR adds an empty Unreleased section above the v0.14.7 release notes.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

This focused bot-generated release-closeout PR follows the documented post-release process and is ready for ordinary release-owner merge review.

Priority: P3
Reviewed head: 6f34f07ff3778be3ab5e66ef1f8113e71f67ea9e

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, policy-aligned release-closeout change with no correctness or security findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: This fleet-generated bot closeout changes no runtime behavior, so contributor real-behavior proof is not applicable.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This fleet-generated bot closeout changes no runtime behavior, so contributor real-behavior proof is not applicable.
Evidence reviewed	5 items	Documented closeout path: The publishing guide directs maintainers after release verification to merge the workflow closeout PR or add the next patch-version Unreleased changelog section. Focused PR diff: The branch adds only the Unreleased heading and blank separator; it changes no runtime code, dependencies, or workflow permissions. Release provenance: v0.14.7 is an annotated release tag at the PR base commit, confirming that this branch follows the released version rather than modifying its release notes.
Findings	None	None.
Security	None	None.

How this fits together

The unified release workflow publishes a verified version from main, while the changelog records dated release notes and then provides an Unreleased staging area for the next release.

flowchart LR
A[Release preparation] --> B[Unified release workflow]
B --> C[Published version tag]
C --> D[Release closeout PR]
D --> E[Unreleased changelog section]
E --> F[Next release notes]

Loading

Before merge

• Complete next step (P2) - A release owner should perform the routine merge approval; no repair work is needed.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog scope	1 file affected; 2 lines added	The branch only opens the next release-notes staging section and changes no runtime or release-workflow behavior.

Technical review

Best possible solution:

Merge this workflow-generated closeout PR so subsequent changes have the documented Unreleased release-note staging area.

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

Not applicable: this release-closeout documentation change has no runtime behavior to reproduce.

Is this the best way to solve the issue?

Yes: the publishing guide explicitly identifies a workflow closeout PR or next Unreleased section as the intended post-release path.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 00a94648f6f2.

Labels

Label justifications:

• P3: This is routine release-note housekeeping with no user-facing runtime impact.
• 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 fleet-generated bot closeout changes no runtime behavior, so contributor real-behavior proof is not applicable.

Evidence

What I checked:

• Documented closeout path: The publishing guide directs maintainers after release verification to merge the workflow closeout PR or add the next patch-version Unreleased changelog section. (docs/publishing.md:73, 00a94648f6f2)
• Focused PR diff: The branch adds only the Unreleased heading and blank separator; it changes no runtime code, dependencies, or workflow permissions. (CHANGELOG.md:3, 6f34f07ff377)
• Release provenance: v0.14.7 is an annotated release tag at the PR base commit, confirming that this branch follows the released version rather than modifying its release notes. (CHANGELOG.md:3, 00a94648f6f2)
• Feature history: The current changelog and unified release workflow were introduced by the v0.14.7 release commit; earlier history also includes release-closeout work. (CHANGELOG.md:1, 00a94648f6f2)
• Structured review limitation: The bundled autoreview helper assembled the commit bundle but could not start because this review environment has no usable temporary directory; direct source and history inspection remained available. (6f34f07ff377)

Likely related people:

• Peter Steinberger: Authored the current v0.14.7 release/changelog commit and the checked-in unified release workflow. (role: recent release-area contributor; confidence: high; commits: 00a94648f6f2; files: CHANGELOG.md, .github/workflows/release-unified.yml)
• Vincent Koc: History associates this contributor with the earlier unified-release restoration and release-closeout sequence. (role: prior release-workflow contributor; confidence: medium; commits: 44849e6aef33, dd7315df3f52; files: .github/workflows/release-unified.yml, 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 (6 earlier review cycles)

• reviewed 2026-08-14T20:22:05.104Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-14T21:57:38.650Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T00:32:10.995Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T03:06:21.335Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T04:46:46.407Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T05:57:22.046Z sha 6f34f07 :: needs maintainer review before merge. :: none