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 13, 2026, 11:06 PM ET / September 14, 2026, 03:06 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased changelog section above the published 0.15.1 notes.

Merge readiness

✅ Ready for maintainer review

The section is still needed on current main. This focused release-maintenance PR has no blocking findings.

Priority: P3
Reviewed head: fa076349eefc1747cc515236871144fe3a8a2dd5

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct maintenance patch with appropriate static validation.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only PR has no runtime behavior requiring contributor proof; the exact text change was inspected.
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 has no runtime behavior requiring contributor proof; the exact text change was inspected.
Evidence reviewed	4 items	Exact introduced change: The pinned base-to-head diff adds only the Unreleased heading and a blank line; existing release notes remain unchanged. Current main and release: GitHub confirmed main remains ab58a53. The v0.15.1 release was published at 2026-09-14T03:01:32Z; current main begins with its versioned notes and lacks Unreleased. Release-history provenance: The GitHub commit patch confirms the release commit renamed Unreleased to 0.15.1 and identifies steipete as its author. Local history listed repeated changelog maintenance; detailed local blame/show encountered an unavailable historical object, so the release patch was verified through GitHub.
Findings	None	None.
Security	None	None.

How this fits together

Discrawl’s changelog separates upcoming changes from published releases and is included in release archives.

flowchart LR
  A[Completed release] --> B[Published version notes]
  B --> C[New Unreleased section]
  C --> D[Future change notes]
  D --> E[Next release changelog]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep a single Unreleased section above the immutable published release notes.

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

Not applicable: this is release bookkeeping, and source inspection confirms the missing heading on main.

Is this the best way to solve the issue?

Yes: adding only the heading restores the existing changelog structure without rewriting released content.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a two-line changelog maintenance 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 has no runtime behavior requiring contributor proof; the exact text change was inspected.

Label justifications:

• P3: This is a two-line changelog maintenance 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 has no runtime behavior requiring contributor proof; the exact text change was inspected.

Evidence

What I checked:

• Exact introduced change: The pinned base-to-head diff adds only the Unreleased heading and a blank line; existing release notes remain unchanged. (CHANGELOG.md:3, fa076349eefc)
• Current main and release: GitHub confirmed main remains ab58a53. The v0.15.1 release was published at 2026-09-14T03:01:32Z; current main begins with its versioned notes and lacks Unreleased. (CHANGELOG.md:3, ab58a5307dda)
• Release-history provenance: The GitHub commit patch confirms the release commit renamed Unreleased to 0.15.1 and identifies steipete as its author. Local history listed repeated changelog maintenance; detailed local blame/show encountered an unavailable historical object, so the release patch was verified through GitHub. (CHANGELOG.md:5, ab58a5307dda)
• Read-only validation: Whitespace validation passed and the final working-tree status was clean. No builds, tests, or bundled review helpers were executed. (CHANGELOG.md:3, fa076349eefc)

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.