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 review in progress

ClawSweeper is reviewing this revision. This supersedes any previous blocked status.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 14, 2026, 11:36 AM ET / 15:36 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased section above the finalized 0.2.1 changelog entry.

Merge readiness

✅ Ready for maintainer review

This is a correct, narrowly scoped release-housekeeping PR. Current main still lacks the next Unreleased section, and no replacement PR was found. The repository profile also prohibits automatic closure.

Priority: P3
Reviewed head: 7592b8c4f08759e3682f824e7277423bedf57e91

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused housekeeping patch with no actionable defect or additional proof requirement.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog update is exempt from contributor runtime proof; source inspection confirms compatibility with the release parsers.
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 update is exempt from contributor runtime proof; source inspection confirms compatibility with the release parsers.
Evidence reviewed	6 items	Complete introduced change: The pinned base-to-head diff adds exactly two lines: the Unreleased heading and a blank line; finalized release content is unchanged. Release parser compatibility: The metadata validator matches only numeric, dated release headings. The release-notes extractor selects the requested version explicitly, so an earlier empty Unreleased section does not change either selection. Current main and published release: GitHub reports main at the pinned base and v0.2.1 published on 2026-09-14T15:33:39Z. Main's changelog starts with finalized 0.2.1 and has no Unreleased section.
Findings	None	None.
Security	None	None.

How this fits together

The changelog records upcoming changes and finalized releases. Release tooling reads its versioned headings to validate metadata and extract release notes.

flowchart LR
  A[Upcoming changes] --> B[Unreleased section]
  B --> C[Finalized version section]
  C --> D[Release metadata validation]
  C --> E[Release notes extraction]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep a single empty Unreleased section above finalized releases for subsequent changelog entries.

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

Not applicable: this PR organizes release documentation rather than repairing a reported runtime failure.

Is this the best way to solve the issue?

Yes: adding one heading is the smallest change, and both release parsers already tolerate it.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 57d99f953677.

Labels

Label changes:

• add P3: This is a two-line changelog housekeeping change with no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This bot-authored changelog update is exempt from contributor runtime proof; source inspection confirms compatibility with the release parsers.

Label justifications:

• P3: This is a two-line changelog housekeeping change 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: This bot-authored changelog update is exempt from contributor runtime proof; source inspection confirms compatibility with the release parsers.

Evidence

What I checked:

• Complete introduced change: The pinned base-to-head diff adds exactly two lines: the Unreleased heading and a blank line; finalized release content is unchanged. (CHANGELOG.md:3, 7592b8c4f087)
• Release parser compatibility: The metadata validator matches only numeric, dated release headings. The release-notes extractor selects the requested version explicitly, so an earlier empty Unreleased section does not change either selection. (scripts/check-release-metadata:13, 7592b8c4f087)
• Current main and published release: GitHub reports main at the pinned base and v0.2.1 published on 2026-09-14T15:33:39Z. Main's changelog starts with finalized 0.2.1 and has no Unreleased section. (CHANGELOG.md:3, 57d99f953677)
• Release history and routing: Changelog history repeatedly identifies Peter Steinberger. GitHub commit metadata maps the latest release commit to steipete and shows it finalized the previous Unreleased heading. Local deeper blame/show inspection encountered unavailable historical objects; the commit API supplied the relevant patch. (CHANGELOG.md:5, 57d99f953677)
• Live state and canonical search: The live pull endpoint confirms this PR is open and unmerged at the pinned head, resolving the older closed issue snapshot. The open-PR listing contains only this PR; the supplied timeline records steipete reopening it. (7592b8c4f087)
• Policy and read-only validation: Read the complete root AGENTS.md and applied its scoped-change guidance. No maintainer-notes directory exists. Whitespace validation passed and the working tree remained clean; builds and tests were not run under the read-only review contract. (AGENTS.md:1, 7592b8c4f087)

Likely related people:

• steipete: 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.