chore: open 0.23.1 unreleased

[steipete]

Restore an empty 0.23.1 - Unreleased section after the 0.23.0 release, following the repository’s existing convention. Keep the published 0.23.0 notes and package versions unchanged.

Validation: focused formatting check and independent P0–P2 review. Merge after the 0.23.0 GitHub Release is published and this exact head passes CI.

[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 changes before merge. Reviewed September 22, 2026, 1:48 AM ET / 05:48 UTC.

ClawSweeper review

What this changes

Adds an empty 0.23.1 Unreleased changelog section while preserving existing release notes and package versions.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The patch is correct and remains useful: current main has no next-version section. Keep this owner-authored PR open pending its explicitly required release publication.

Priority: P3
Reviewed head: 2422e86fb8dc486ebfb222a8985d988b95f50712

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct housekeeping patch; the publication prerequisite affects timing rather than patch quality.
Proof confidence	🌊 off-meta tidepool	Not applicable: This owner-authored changelog-only PR is exempt from contributor runtime proof; it changes no stored-data contract.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This owner-authored changelog-only PR is exempt from contributor runtime proof; it changes no stored-data contract.
Evidence reviewed	5 items	Complete introduced patch: The pinned delta adds only a heading and blank line; existing notes and all version sources are unchanged. git diff --check passed. Existing release extraction remains compatible: Release-note extraction selects the requested version explicitly and stops at the next heading, so the preceding empty section does not replace 0.23.0 notes. Release publication condition remains outstanding: The PR body explicitly requires publication of the 0.23.0 GitHub Release before merge. The release endpoint returned HTTP 404; the release listing still starts at v0.22.0.
Findings	None	None.
Security	None	None.

How this fits together

The changelog collects changes for upcoming releases. Release tooling extracts the section matching the package version for publication.

flowchart LR
  A[Future changes] --> B[Unreleased section]
  B --> C[Dated release section]
  D[Package version] --> E[Release note extraction]
  C --> E
  E --> F[Published release notes]

Loading

Before merge

• Complete next step (P2) - Confirm v0.23.0 is published on GitHub before merging, as required by the PR body.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Retain a separate upcoming-release section without changing published notes or prematurely bumping package versions.

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

Not applicable: this PR adds a changelog placeholder and reports no runtime defect.

Is this the best way to solve the issue?

Yes: the two-line addition follows the preceding unreleased-heading convention and preserves version-specific note extraction.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add P3: This is a two-line release 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 owner-authored changelog-only PR is exempt from contributor runtime proof; it changes no stored-data contract.

Label justifications:

• P3: This is a two-line release 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 owner-authored changelog-only PR is exempt from contributor runtime proof; it changes no stored-data contract.

Evidence

What I checked:

• Complete introduced patch: The pinned delta adds only a heading and blank line; existing notes and all version sources are unchanged. git diff --check passed. (CHANGELOG.md:3, 2422e86fb8dc)
• Existing release extraction remains compatible: Release-note extraction selects the requested version explicitly and stops at the next heading, so the preceding empty section does not replace 0.23.0 notes. (scripts/release.sh:100, 2422e86fb8dc)
• Release publication condition remains outstanding: The PR body explicitly requires publication of the 0.23.0 GitHub Release before merge. The release endpoint returned HTTP 404; the release listing still starts at v0.22.0.
• Merged release preparation and routing history: GitHub confirms chore(release): prepare 0.23.0 #484 merged at the current main commit. Its changelog patch converts the previous Unreleased heading to the dated 0.23.0 heading, and identifies steipete as the commit author. (CHANGELOG.md:5, 7ce8f68b9daa)
• Current main and inspection limitation: The live main branch remains at the pinned base. Recent changelog history was readable, but deeper history searches and blame failed on an unavailable promisor object; no introduction attribution relies on those failed operations. (CHANGELOG.md, 7ce8f68b9daa)

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.