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 26, 2026, 7:03 AM ET / 11:03 UTC.

ClawSweeper review

What this changes

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

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open: current main still starts with the v0.9.2 section and lacks the requested Unreleased heading. This is a clean, focused release-bookkeeping change with no correctness or security finding.

Priority: P3
Reviewed head: fe353a46d17211eb0e1d5328521ed4984f17016f

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct release-maintenance patch with no runtime or security concerns found.
Proof confidence	🌊 off-meta tidepool	Not applicable: Not applicable: this bot-authored release-bookkeeping PR changes only the changelog and has no runtime behavior to demonstrate.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: Not applicable: this bot-authored release-bookkeeping PR changes only the changelog and has no runtime behavior to demonstrate.
Evidence reviewed	4 items	Focused branch change: The PR head adds only the empty Unreleased heading and separator above v0.9.2. Still absent from current main: Current main’s changelog begins directly with v0.9.2, so the requested heading is not already implemented there. Release-process context: Repository documentation describes preparing and landing a dated changelog section on protected main before dispatching the official release workflow.
Findings	None	None.
Security	None	None.

How this fits together

Gitcrawl’s release process prepares a changelog on protected main before the official GitHub Actions release workflow freezes it into signed archives. This PR creates the top-level collection point where subsequent unreleased notes can be recorded.

flowchart LR
A[Release notes] --> B[Unreleased changelog section]
B --> C[Dated release section]
C --> D[Protected main]
D --> E[Official release workflow]
E --> F[Signed release archives]

Loading

Before merge

• Complete next step (P2) - No repair lane is needed: this is already a focused release-maintenance PR awaiting ordinary release-owner merge review.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog scope	1 file changed; 2 added, 0 removed	The patch is isolated to release-note staging and does not modify runtime code or dependencies.

Technical review

Best possible solution:

Merge the isolated heading so future release notes have a clear staging section while keeping the dated v0.9.2 entry unchanged.

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

Not applicable: this is a release-bookkeeping change, and current main directly shows the requested heading is still absent.

Is this the best way to solve the issue?

Yes. Adding one empty top-level section is the narrowest maintainable way to stage notes for the next release without changing the completed v0.9.2 record.

AGENTS.md: found, but no applicable review policy affected this item.

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

Labels

Label justifications:

• P3: This is low-risk release bookkeeping with no user-facing regression or operational urgency.
• 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: Not applicable: this bot-authored release-bookkeeping PR changes only the changelog and has no runtime behavior to demonstrate.

Evidence

What I checked:

• Focused branch change: The PR head adds only the empty Unreleased heading and separator above v0.9.2. (CHANGELOG.md:3, fe353a46d172)
• Still absent from current main: Current main’s changelog begins directly with v0.9.2, so the requested heading is not already implemented there. (CHANGELOG.md:3, becc7bb8b8f2)
• Release-process context: Repository documentation describes preparing and landing a dated changelog section on protected main before dispatching the official release workflow. (docs/releasing.md:22, becc7bb8b8f2)
• Changelog provenance: Blame attributes the current v0.9.2 release heading to the release-preparation commit by Peter Steinberger, connecting the affected ledger to the release workflow history. (CHANGELOG.md:3, 648098df8bf7)

Likely related people:

• Peter Steinberger: Current-main blame attributes the v0.9.2 changelog section to the release-preparation commit. (role: release changelog author; confidence: medium; commits: 648098df8bf7; files: CHANGELOG.md, docs/releasing.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 (18 earlier review cycles; latest 8 shown)

• reviewed 2026-08-23T22:09:05.831Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-24T03:14:10.167Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-24T10:07:35.112Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-24T15:08:39.013Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-24T22:01:02.137Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T01:15:33.933Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T07:52:06.787Z sha fe353a4 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T22:09:22.492Z sha fe353a4 :: needs maintainer review before merge. :: none