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 changes before merge. Reviewed August 14, 2026, 11:06 PM ET / August 15, 2026, 03:06 UTC.

ClawSweeper review

What this changes

The PR adds a generic empty Unreleased heading above the v0.37.0 changelog section.

Merge readiness

⚠️ Ready for maintainer review - 3 items remain

Keep this PR open: it still has the two previously reported release-closeout defects on the unchanged head, so merging it would leave the next development transition incomplete.

Priority: P2
Reviewed head: 6a3d0264696bb2886f2fc16f2895b298a78637b5

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The release-closeout intent is clear, but the patch omits two required pieces of the established transition.
Proof confidence	🌊 off-meta tidepool	Not applicable: This is a repository-generated release-closeout PR; source contract and release-helper regression coverage are the applicable validation evidence.
Patch quality	🦐 gold shrimp (3/6)	2 actionable review findings remain.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This is a repository-generated release-closeout PR; source contract and release-helper regression coverage are the applicable validation evidence.
Evidence reviewed	5 items	PR remains incomplete: The unchanged branch adds only a generic heading and does not update the development-version file required by the release transition. Release helper contract: The supported closeout helper emits ## <next patch> - Unreleased and writes the released version with a -dev suffix to the version file. Regression coverage: The existing closeout test asserts both the versioned next-patch heading and the -dev version transition.
Findings	2 actionable findings	[P2] Use the versioned next-patch heading [P2] Complete the development-version transition
Security	None	None.

How this fits together

The release closeout follows a verified version tag and prepares the next patch development cycle. It updates the changelog section and the CLI development-version marker used by subsequent release work.

flowchart LR
  A[Verified v0.37.0 release] --> B[Release closeout]
  B --> C[Next patch calculation]
  C --> D[Versioned changelog section]
  C --> E[Development version marker]
  D --> F[Next release workflow]
  E --> F

Loading

Before merge

• Use the versioned next-patch heading (P2) - Replace the generic heading with ## 0.37.1 - Unreleased. The existing closeout helper detects only semantic-version headings, so this line will not prevent a later closeout from inserting a second section.
• Complete the development-version transition (P2) - Update internal/cmd/VERSION to v0.37.0-dev with this closeout. The documented helper and its regression test make the changelog and version update one transition; leaving the current released value breaks that contract.
• Resolve merge risk (P1) - Merging the generic heading means the next closeout will not recognize it as an existing versioned section and can add a second Unreleased section; the missing -dev marker also leaves development-version state inconsistent.

Findings

• [P2] Use the versioned next-patch heading — CHANGELOG.md:3
• [P2] Complete the development-version transition — CHANGELOG.md:3

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Closeout transition	1 file changed; 1 required counterpart omitted	The documented helper and regression test require changelog and version-marker updates together.

Merge-risk options

Maintainer options:

1. Complete the atomic release transition (recommended)
   Replace the generic heading with the versioned next-patch heading and include the required development-version file update before merging.

Copy recommended automerge instruction

@clawsweeper automerge

Special instructions:
Replace the generic heading with `## 0.37.1 - Unreleased`, set `internal/cmd/VERSION` to `v0.37.0-dev`, and run `scripts/test-start-next-release.sh`.

Technical review

Best possible solution:

Regenerate the closeout using the established helper contract so the next patch heading is ## 0.37.1 - Unreleased and the version file becomes v0.37.0-dev.

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

Yes, at source level: the helper recognizes only semantic-version Unreleased headings and its test requires both the heading and -dev version update; this PR provides neither complete transition.

Is this the best way to solve the issue?

No. The existing helper, test, and release guide define a narrower atomic transition than this one-file generic heading.

Full review comments:

• [P2] Use the versioned next-patch heading — CHANGELOG.md:3
  Replace the generic heading with ## 0.37.1 - Unreleased. The existing closeout helper detects only semantic-version headings, so this line will not prevent a later closeout from inserting a second section.
  Confidence: 0.99
• [P2] Complete the development-version transition — CHANGELOG.md:3
  Update internal/cmd/VERSION to v0.37.0-dev with this closeout. The documented helper and its regression test make the changelog and version update one transition; leaving the current released value breaks that contract.
  Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• remove rating: 🦪 silver shellfish: Current PR rating is rating: 🦐 gold shrimp, so this older rating label is no longer current.

Label justifications:

• P2: This is a bounded release-maintenance defect that can disrupt the next release closeout but does not affect current runtime users.
• merge-risk: 🚨 automation: The generic heading bypasses the release helper's semantic-version detector and can cause duplicate closeout sections.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a repository-generated release-closeout PR; source contract and release-helper regression coverage are the applicable validation evidence.

Evidence

Acceptance criteria:

• [P1] scripts/test-start-next-release.sh.
• [P1] Verify the PR changes only CHANGELOG.md and internal/cmd/VERSION and contains exactly one ## 0.37.1 - Unreleased heading.

What I checked:

• PR remains incomplete: The unchanged branch adds only a generic heading and does not update the development-version file required by the release transition. (CHANGELOG.md:3, 6a3d0264696b)
• Release helper contract: The supported closeout helper emits ## <next patch> - Unreleased and writes the released version with a -dev suffix to the version file. (scripts/start-next-release.sh:35, 45b5d766e137)
• Regression coverage: The existing closeout test asserts both the versioned next-patch heading and the -dev version transition. (scripts/test-start-next-release.sh:29, 45b5d766e137)
• Documented release procedure: The release guide says this closeout must land both the next-patch Unreleased section and the released-version -dev marker. (docs/RELEASING.md:53, 45b5d766e137)
• Review continuity: The current head is the same SHA reviewed previously, so both prior findings remain unresolved rather than being newly discovered. (CHANGELOG.md:3, 6a3d0264696b)

Likely related people:

• Peter Steinberger: Current main history attributes the release helper, its regression test, release guide, and v0.37.0 preparation to this release-area change. (role: release-workflow contributor; confidence: medium; commits: 45b5d766e137; files: scripts/start-next-release.sh, scripts/test-start-next-release.sh, docs/RELEASING.md)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Use the versioned 0.37.1 Unreleased heading.
• Update the development version and run scripts/test-start-next-release.sh.

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 (2 earlier review cycles)

• reviewed 2026-08-14T20:14:34.775Z sha 6a3d026 :: needs changes before merge. :: [P2] Use the versioned Unreleased heading | [P2] Complete the development-version transition
• reviewed 2026-08-14T21:57:11.204Z sha 6a3d026 :: needs changes before merge. :: [P2] Use the versioned next-patch heading | [P2] Complete the embedded development-version transition