chore: open unreleased

[steipete]

Reopen the empty Unreleased section after the 0.4.11 release, preserving the complete 0.4.11 and 0.4.10 changelog sections.

Keep this PR in draft until the signed 0.4.11 binary release is published and verified and the requested notes-only 0.4.10 GitHub Release exists.

Validation: unchanged released text, clean diff checks, and independent P0–P2 autoreview.

[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 13, 2026, 10:46 PM ET / September 14, 2026, 02:46 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased changelog section while preserving the complete 0.4.11 and 0.4.10 release notes.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The patch is correct and still absent from main. Keep this collaborator-authored PR open in draft under its explicit release prerequisites.

Priority: P3
Reviewed head: 11f0867ababbf1bbb2a3b15670706865d648d300

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct housekeeping patch whose explicit release timing remains separate from patch quality.
Proof confidence	🌊 off-meta tidepool	Not applicable: This collaborator-authored changelog-only PR is exempt from contributor runtime proof; static inspection confirms the released text and extraction behavior remain intact.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This collaborator-authored changelog-only PR is exempt from contributor runtime proof; static inspection confirms the released text and extraction behavior remain intact.
Evidence reviewed	5 items	Complete introduced change: The pinned diff adds only the Unreleased heading and a blank line; all existing release text remains unchanged. The read-only diff whitespace check passed. Current main still lacks the heading: The main changelog begins with the dated 0.4.11 section. A live REST check confirmed main remains at the supplied base SHA. Release prerequisites: The captured PR body explicitly requires verified published signed 0.4.11 binaries and a notes-only 0.4.10 release before leaving draft. The GitHub releases response listed v0.4.9 as the newest published release and contained neither requested release.
Findings	None	None.
Security	None	None.

How this fits together

The changelog records changes to goplaces, a Go client and CLI for Google Places and Routes. Release tooling extracts dated sections to produce published release notes.

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

Loading

Before merge

• Complete next step (P2) - Keep this PR in draft until signed 0.4.11 binaries are published and verified and the notes-only 0.4.10 GitHub Release exists, then mark it ready.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Preserve the released notes and use the empty Unreleased section for subsequent changes once the specified release handoff is complete.

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

Not applicable: this is changelog housekeeping, and the complete diff establishes the intended text change.

Is this the best way to solve the issue?

Yes: adding an empty heading is the narrowest change, and the existing dated-section extraction preserves release-note behavior.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a two-line 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 collaborator-authored changelog-only PR is exempt from contributor runtime proof; static inspection confirms the released text and extraction behavior remain intact.

Label justifications:

• P3: This is a two-line 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 collaborator-authored changelog-only PR is exempt from contributor runtime proof; static inspection confirms the released text and extraction behavior remain intact.

Evidence

What I checked:

• Complete introduced change: The pinned diff adds only the Unreleased heading and a blank line; all existing release text remains unchanged. The read-only diff whitespace check passed. (CHANGELOG.md:3, 11f0867ababb)
• Current main still lacks the heading: The main changelog begins with the dated 0.4.11 section. A live REST check confirmed main remains at the supplied base SHA. (CHANGELOG.md:3, c0cdace7197b)
• Release prerequisites: The captured PR body explicitly requires verified published signed 0.4.11 binaries and a notes-only 0.4.10 release before leaving draft. The GitHub releases response listed v0.4.9 as the newest published release and contained neither requested release.
• Release extraction remains compatible: Released-note extraction searches for the exact dated version heading and stops at the following section. The separate 0.4.11 rollup also selects the dated 0.4.10 section explicitly, so a preceding empty heading does not change either result. The associated release-note tests were read, not executed. (scripts/release-local:1172, 11f0867ababb)
• Merged release history and routing: Changelog history repeatedly identifies Peter Steinberger. GitHub REST identifies steipete as the author of the current-main release commit and confirms chore(release): cut 0.4.11 #56 merged at that SHA. Its patch adds the dated 0.4.11 section, not the proposed Unreleased section. Local historical patch/blame inspection encountered an unavailable promisor object; the exact commit patch was inspected through GitHub REST instead. (CHANGELOG.md:5, c0cdace7197b)

Likely related people:

• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; 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.