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, 2:00 AM ET / 06:00 UTC.

ClawSweeper review

What this changes

This PR adds an empty Unreleased section above the v0.8.5 changelog entry for future release notes.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

Keep open: current main still starts its changelog with v0.8.5, so it has not incorporated this PR’s Unreleased heading. The focused release-maintenance change is clean and awaits routine maintainer merge.

Priority: P3
Reviewed head: a3c85c2aa18e44b7878fc4b4e28f76224f2bd7bf

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The patch is a clean, narrowly scoped release-note preparation change with no correctness finding.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only PR has no runtime behavior requiring 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 changelog-only PR has no runtime behavior requiring contributor proof.
Evidence reviewed	3 items	Current main remains without the heading: Current main’s changelog begins with the v0.8.5 entry; it does not contain an Unreleased section. Focused branch diff: The branch adds exactly the Unreleased heading and its separating blank line above v0.8.5. Release-history provenance: The current v0.8.5 changelog entry was introduced by the tagged release-preparation commit; the new heading is a later bot-authored follow-up.
Findings	None	None.
Security	None	None.

How this fits together

Slacrawl’s changelog records released behavior and provides a holding section for changes awaiting the next release. Release automation creates versioned entries, while subsequent work accumulates under Unreleased.

flowchart LR
A[Release workflow] --> B[Versioned changelog entry]
B --> C[Unreleased section]
D[Future changes] --> C
C --> E[Next release notes]

Loading

Before merge

• Resolve merge risk (P1) - The branch is behind current main; refresh the merge view before landing, although GitHub reports it as mergeable.
• Complete next step (P2) - No repair is needed; routine maintainer merge review is the remaining action.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog scope	1 file changed, +2/-0 lines	The branch is limited to the release-note heading and introduces no runtime or dependency surface.

Merge-risk options

Maintainer options:

1. Decide the mitigation before merge
   Merge the narrow release-owned changelog preparation once the maintainer confirms the release sequencing remains appropriate.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Technical review

Best possible solution:

Merge the narrow release-owned changelog preparation once the maintainer confirms the release sequencing remains appropriate.

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

Not applicable: this PR changes only changelog structure and does not report runtime behavior.

Is this the best way to solve the issue?

Yes. Adding the empty heading is the smallest maintainable way to prepare the post-v0.8.5 changelog.

AGENTS.md: not found in the target repository.

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

Labels

Label justifications:

• P3: This is a small release-note maintenance change 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 bot-authored changelog-only PR has no runtime behavior requiring contributor proof.

Evidence

What I checked:

• Current main remains without the heading: Current main’s changelog begins with the v0.8.5 entry; it does not contain an Unreleased section. (CHANGELOG.md:3, 526888485c56)
• Focused branch diff: The branch adds exactly the Unreleased heading and its separating blank line above v0.8.5. (CHANGELOG.md:3, a3c85c2aa18e)
• Release-history provenance: The current v0.8.5 changelog entry was introduced by the tagged release-preparation commit; the new heading is a later bot-authored follow-up. (CHANGELOG.md:3, b793612bfa8a)

Likely related people:

• Peter Steinberger: Authored the current v0.8.5 release-preparation commit that established the changelog entry this PR follows. (role: release-entry author and recent changelog contributor; confidence: high; commits: b793612bfa8a; 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 (8 earlier review cycles)

• reviewed 2026-08-14T20:02:13.279Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T04:01:47.292Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T07:04:39.305Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T09:11:12.459Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T11:05:24.463Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-15T20:54:50.327Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-17T13:33:46.223Z sha a3c85c2 :: needs maintainer review before merge. :: none
• reviewed 2026-08-21T16:05:44.050Z sha a3c85c2 :: needs maintainer review before merge. :: none