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 complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 7, 2026, 1:53 PM ET / 17:53 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased changelog section above the finalized 0.2.5 release notes.

Merge readiness

✅ Ready for maintainer review

The release follow-up remains useful: current main has no Unreleased section. The two-line addition preserves finalized notes and is compatible with the repository’s release-note readers; no blocking defect was found.

Priority: P3
Reviewed head: eff10bf2d8c1757afd5491b573989a76651423cc

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct release housekeeping patch with no material follow-up needed.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only PR is exempt from contributor runtime proof; the visible heading and release-reader compatibility were inspected directly.
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 is exempt from contributor runtime proof; the visible heading and release-reader compatibility were inspected directly.
Evidence reviewed	5 items	Verified introduced change: The independently inspected base-to-head diff adds only the Unreleased heading and a blank line. Existing release contents are unchanged; the whitespace check passed. Current main and release boundary: The inspected main changelog starts with finalized 0.2.5 notes and lacks an Unreleased section. The local v0.2.5 tag points at the supplied main revision, consistent with the captured latest-release metadata. Release readers tolerate the heading: The release-note reader begins output only at the requested numeric version heading. The separately inspected scripts/check-release-metadata selects the first numeric version heading, so the new unversioned heading does not alter either selection.
Findings	None	None.
Security	None	None.

How this fits together

The changelog records eightctl’s development changes and published releases. Release tooling extracts the requested version’s section and checks the latest finalized version against package metadata.

flowchart LR
  A[Development changes] --> B[Unreleased section]
  B --> C[Finalized release section]
  C --> D[Version metadata check]
  C --> E[Release note extraction]
  E --> F[Published release notes]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep one empty development section above the unchanged published release history.

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

Not applicable: this is release housekeeping, and source inspection confirms the heading is absent from main and present in the proposed branch.

Is this the best way to solve the issue?

Yes: the minimal heading addition provides the next development section without changing version metadata or published notes.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a small post-release 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-only PR is exempt from contributor runtime proof; the visible heading and release-reader compatibility were inspected directly.

Label justifications:

• P3: This is a small post-release 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-only PR is exempt from contributor runtime proof; the visible heading and release-reader compatibility were inspected directly.

Evidence

What I checked:

• Verified introduced change: The independently inspected base-to-head diff adds only the Unreleased heading and a blank line. Existing release contents are unchanged; the whitespace check passed. (CHANGELOG.md:7, eff10bf2d8c1)
• Current main and release boundary: The inspected main changelog starts with finalized 0.2.5 notes and lacks an Unreleased section. The local v0.2.5 tag points at the supplied main revision, consistent with the captured latest-release metadata. (CHANGELOG.md:7, bfc6abd5bf7d)
• Release readers tolerate the heading: The release-note reader begins output only at the requested numeric version heading. The separately inspected scripts/check-release-metadata selects the first numeric version heading, so the new unversioned heading does not alter either selection. (scripts/release-notes:12, eff10bf2d8c1)
• Release history and routing: Recent changelog history includes release preparation by Peter Steinberger and an earlier bot-created development section. Broader follow-history and blame inspection encountered unavailable historical objects and a DNS failure; no exact source-line introduction is claimed. (CHANGELOG.md, bfc6abd5bf7d)
• Discussion and repository policy: The captured complete PR body identifies this as fleet release closeout work. Discussion contains only filtered ClawSweeper bot comments, with no human review comments. No target AGENTS.md or maintainer-notes directory was found. The supplied personal-repository profile prohibits automatic closure.

Likely related people:

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

[steipete]

Verified release closeout for v0.2.5, from bfc6abd5bf7d9e3668fd415bf349556b8690888a:

• Release workflow succeeded: https://github.com/steipete/eightctl/actions/runs/34148578384 . Signing, notarization, and independent arm64/x86_64 verification passed.
• Downloaded all 11 assets; all 10 checksum entries and GitHub asset digests match. The inventory names the release commit, and the release body and RELEASE-NOTES.md exactly match the finalized changelog.
• codesign --verify --strict --check-notarization passed for all three macOS binaries. Native and universal artifacts print 0.2.5.
• The Go proxy returns github.com/steipete/eightctl v0.2.5.
• Homebrew handoff succeeded: https://github.com/steipete/homebrew-tap/actions/runs/34149370650 . All four formula URLs/hashes match the verified inventory. The installed tap binary prints 0.2.5 and brew test steipete/tap/eightctl passes.
• This two-line changelog closeout passes metadata validation and independent branch autoreview through P2. Squash title: chore: open 0.2.6 unreleased.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: chore: open next Unreleased section This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.