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 31, 2026, 4:54 AM ET / 08:54 UTC.

ClawSweeper review

What this changes

The branch adds an empty Unreleased heading above the v0.8.6 notes in CHANGELOG.md.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open: this is the documented release-closeout change, and current main does not yet contain its new Unreleased section. The patch is focused and has no correctness finding.

Priority: P3
Reviewed head: 2fca7302f82ee7151c7cb92163b8887b788d3aac

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The patch is a focused documentation change aligned with the repository’s release-closeout convention.
Proof confidence	🌊 off-meta tidepool	Not applicable: The branch changes only CHANGELOG.md, so external runtime proof is not required.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The branch changes only CHANGELOG.md, so external runtime proof is not required.
Evidence reviewed	4 items	Documented release-closeout contract: The contribution guide states that the shared release workflow publishes verified bytes and opens the next Unreleased changelog pull request. Introduced changelog scope: The complete introduced diff adds only the Unreleased heading and blank separator before v0.8.6. Established changelog convention: Current changelog history includes a prior bot-authored commit with the same release-closeout purpose.
Findings	None	None.
Security	None	None.

How this fits together

Slacrawl’s changelog records shipped releases and provides a staging section where subsequent changes are collected. The unified release workflow opens that section after publishing a verified release.

flowchart LR
A[Verified release] --> B[Unified release workflow]
B --> C[Release closeout]
C --> D[Unreleased changelog section]
D --> E[Future release notes]

Loading

Before merge

• Complete next step (P2) - This PR needs ordinary maintainer review and the pending release-check conclusion; no repair lane is needed.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog scope	2 added, 0 removed; 1 file affected	The documentation-only diff is restricted to the release-note staging heading.

Technical review

Best possible solution:

Merge the documented release-closeout update so subsequent changes have the standard staging section above v0.8.6.

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

Not applicable: the pull request changes release-note structure only, and the rendered changelog content is directly inspectable.

Is this the best way to solve the issue?

Yes: adding the documented Unreleased staging heading directly above the verified v0.8.6 notes is the narrowest release-closeout change.

AGENTS.md: not found in the target repository.

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

Labels

Label justifications:

• P3: This is a two-line changelog maintenance update with no runtime 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: The branch changes only CHANGELOG.md, so external runtime proof is not required.

Evidence

What I checked:

• Documented release-closeout contract: The contribution guide states that the shared release workflow publishes verified bytes and opens the next Unreleased changelog pull request. (CONTRIBUTING.md:61, dd2608b91f4f)
• Introduced changelog scope: The complete introduced diff adds only the Unreleased heading and blank separator before v0.8.6. (CHANGELOG.md:3, 2fca7302f82e)
• Established changelog convention: Current changelog history includes a prior bot-authored commit with the same release-closeout purpose. (CHANGELOG.md:1, fde1534c6a60)
• Release boundary: The v0.8.6 tag contains the PR base commit, while no tag contains this unmerged PR head; the proposed staging section is intentionally post-release. (CHANGELOG.md:5, dd2608b91f4f)

Likely related people:

• github-actions[bot]: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

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 (1 earlier review cycle)

• reviewed 2026-08-31T08:51:18.757Z sha 2fca730 :: needs maintainer review before merge. :: none