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]

Codex review: needs maintainer review before merge. Reviewed July 27, 2026, 2:43 AM ET / 06:43 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased section above the v0.7.11 entry in CHANGELOG.md so subsequent changes have a release-note staging area.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep this PR open for the release workflow: its two-line changelog update is not yet on current main, and the supplied context identifies it as the fleet release closeout step after v0.7.11. The available timeline contains no substantive maintainer objection or competing implementation.

Priority: P3
Reviewed head: 1a7ab4824f4a96c930c9d93d59f9100ddcc5f230

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A narrowly scoped automated release bookkeeping patch with a directly auditable two-line diff.
Proof confidence	🌊 off-meta tidepool	Not applicable: This bot-authored changelog-only release-closeout PR does not require runtime behavior proof.
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 PR does not require runtime behavior proof.
Evidence reviewed	3 items	PR diff: The supplied pull-request diff adds exactly two lines: an Unreleased heading and a blank separator before the v0.7.11 release entry. Release-closeout provenance: The PR body states that this change is created by the fleet release closeout stage after the verified v0.7.11 release; the branch is based on current main at 684c7a4. Current release context: Repository context identifies v0.7.11 at 498f626 as the latest release; this PR opens the next post-release changelog section rather than changing shipped release content.
Findings	None	None.
Security	None	None.

How this fits together

The release closeout workflow updates the repository changelog after a verified version is published. New development entries then accumulate under the top-level Unreleased section before the next release is cut.

flowchart TD
  A[Verified release v0.7.11] --> B[Release closeout workflow]
  B --> C[Changelog]
  C --> D[Unreleased section]
  D --> E[Future release notes]
  E --> F[Next published release]

Loading

Before merge

• Complete next step (P2) - No repair lane is needed; this is a normal, narrowly scoped release-closeout PR awaiting ordinary merge handling.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog scope	1 file affected; 2 lines added; 0 removed	The branch is limited to opening the next release-note section and does not alter application code or released notes.

Technical review

Best possible solution:

Merge the minimal release-closeout update so future release notes are collected under a fresh Unreleased section.

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

Not applicable: this PR is release bookkeeping rather than a report of broken behavior. The observable change is fully represented by the two-line changelog diff.

Is this the best way to solve the issue?

Yes: adding the empty heading directly above the most recent release is the narrowest way to restore a staging area for the next release notes.

AGENTS.md: unclear because the file could not be read completely.

Codex review notes: model internal, reasoning high; reviewed against 684c7a4fe5ca.

Labels

Label changes:

• add P3: This is low-risk release bookkeeping with no runtime or user-flow change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Label justifications:

• P3: This is low-risk release bookkeeping with no runtime or user-flow change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Evidence

What I checked:

• PR diff: The supplied pull-request diff adds exactly two lines: an Unreleased heading and a blank separator before the v0.7.11 release entry. (CHANGELOG.md:3, 1a7ab4824f4a)
• Release-closeout provenance: The PR body states that this change is created by the fleet release closeout stage after the verified v0.7.11 release; the branch is based on current main at 684c7a4. (CHANGELOG.md:3, 1a7ab4824f4a)
• Current release context: Repository context identifies v0.7.11 at 498f626 as the latest release; this PR opens the next post-release changelog section rather than changing shipped release content. (CHANGELOG.md:5, 498f62693f6f)

Likely related people:

• github-actions[bot]: The proposed change and its single commit are explicitly attributed to the automated fleet release closeout stage. (role: release automation origin; confidence: high; commits: 1a7ab4824f4a; 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.

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