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 27, 2026, 10:47 PM ET / August 28, 2026, 02:47 UTC.

ClawSweeper review

What this changes

The PR adds an empty Unreleased section above the v0.14.7 release notes to begin the next development changelog cycle.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

This PR remains necessary: current main still begins with the v0.14.7 section, and the release checklist explicitly calls for an Unreleased section after closeout. No introduced correctness or security defect was found.

Priority: P3
Reviewed head: 6f34f07ff3778be3ab5e66ef1f8113e71f67ea9e

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The focused patch follows the documented release-closeout convention and has no identified correctness defect.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only release-closeout change 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: This bot-authored changelog-only release-closeout change has no runtime behavior to demonstrate.
Evidence reviewed	4 items	Current main lacks the heading: The fetched current-main changelog starts with the v0.14.7 dated section, so the requested next-cycle Unreleased heading is not already implemented. Documented release procedure: The current release checklist says to merge the workflow closeout PR or add the next patch-version Unreleased changelog section. Established closeout practice: History contains a prior automated "open next Unreleased section" change, supporting this as an established release-closeout convention.
Findings	None	None.
Security	None	None.

How this fits together

The changelog records crawlkit releases and upcoming changes for downstream Go users. This PR changes only the release-notes entry point and does not affect runtime packages or release artifacts.

flowchart LR
A[Unified release workflow] --> B[Versioned release notes]
B --> C[Closeout pull request]
C --> D[Unreleased section]
D --> E[Future development notes]

Loading

Before merge

• Resolve merge risk (P1) - The branch is based on v0.14.7 while main has advanced; refresh GitHub's three-way merge state before landing, although the reviewed change is limited to the heading.
• Complete next step (P2) - No repair lane is needed; the remaining action is ordinary maintainer merge review with a refreshed merge state.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog delta	2 added, 0 removed; 1 Markdown file	The change is confined to the documented post-release heading and has no runtime or API surface.

Merge-risk options

Maintainer options:

1. Decide the mitigation before merge
   Merge the focused closeout change so future development changes have the documented Unreleased destination.
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 focused closeout change so future development changes have the documented Unreleased destination.

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

Not applicable: this is a changelog-structure change rather than a reported runtime defect.

Is this the best way to solve the issue?

Yes: adding the heading directly follows the repository's documented post-release closeout path.

AGENTS.md: found and applied where relevant.

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

Labels

Label justifications:

• P3: This is low-risk release-note maintenance with no runtime user 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 release-closeout change has no runtime behavior to demonstrate.

Evidence

What I checked:

• Current main lacks the heading: The fetched current-main changelog starts with the v0.14.7 dated section, so the requested next-cycle Unreleased heading is not already implemented. (CHANGELOG.md:1, 5309f4cd9246)
• Documented release procedure: The current release checklist says to merge the workflow closeout PR or add the next patch-version Unreleased changelog section. (docs/publishing.md:73, 5309f4cd9246)
• Established closeout practice: History contains a prior automated "open next Unreleased section" change, supporting this as an established release-closeout convention. (CHANGELOG.md:1, 3d4479797b53)
• Structured-review infrastructure limitation: The repository-required autoreview helper could not start because the review environment has no usable temporary directory; the source and history checks above completed read-only. (6f34f07ff377)

Likely related people:

• Peter Steinberger: Authored the v0.14.7 release preparation and the release changelog correction immediately preceding this closeout change. (role: recent release-process contributor; confidence: high; commits: 00a94648f6f2, 67e034c85127; files: CHANGELOG.md, docs/publishing.md)
• Vincent Koc: Has substantial changelog history and authored the previous v0.14.6 Unreleased-section change. (role: release-changelog contributor; confidence: high; commits: 44849e6aef33; 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 (26 earlier review cycles; latest 8 shown)

• reviewed 2026-08-24T23:22:12.340Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T01:15:50.831Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T07:15:31.983Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-25T13:15:54.887Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-26T03:13:40.910Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-26T11:04:00.742Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-26T19:35:15.737Z sha 6f34f07 :: needs maintainer review before merge. :: none
• reviewed 2026-08-27T05:47:49.177Z sha 6f34f07 :: needs maintainer review before merge. :: none

[steipete]

Superseded: #97 (merged) already opened the Unreleased changelog section with the dependency-refresh entries.