chore: reopen unreleased after 0.3.8

[steipete]

Restore the empty Unreleased section after the verified 0.3.8 publication and Homebrew upgrade. The finalized release notes and version remain unchanged.

Release: https://github.com/openclaw/remindctl/releases/tag/v0.3.8

Both native architectures passed the draft verifier (run 35979995779) and published verifier (run 35980369170). The authorized host check passed the notarized codesign constraint, first execution with manually applied browser-style quarantine, and read-only Reminders access without a new prompt. This does not claim clean-VM or cross-Team TCC migration proof.

The Homebrew helper verified the archive digest, updated the formula, upgraded to 0.3.8, passed brew test, and verified the installed universal binary's signature and notarization. Formula update: steipete/homebrew-tap@bb98426.

Codex autoreview found no actionable closeout findings. Exact-head CI is required before merge.

[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 24, 2026, 5:26 AM ET / 09:26 UTC.

ClawSweeper review

What this changes

Adds an empty Unreleased heading above the finalized 0.3.8 changelog entry for future release notes.

Merge readiness

✅ Ready for maintainer review

Keep open: current main lacks the reopened Unreleased section, and this PR follows the documented closeout sequence after the published 0.3.8 release and Homebrew formula update.

Priority: P3
Reviewed head: 5d936fa195d4c019dbf76d539c081370d8efd13f

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A small, policy-aligned closeout with verified publication context and no identified patch defect.
Proof confidence	🌊 off-meta tidepool	Not applicable: The added heading precedes the version section consumed by the release-note extractor; this collaborator-authored changelog closeout has no contributor runtime-proof gate or stored-data contract change.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The added heading precedes the version section consumed by the release-note extractor; this collaborator-authored changelog closeout has no contributor runtime-proof gate or stored-data contract change.
Evidence reviewed	7 items	Introduced change: The PR adds only the empty Unreleased heading and a blank line above 0.3.8. Current-main gap: The current main changelog begins with the finalized 0.3.8 section and has no Unreleased heading. Closeout policy: The release guide directs reopening Unreleased only after GitHub and Homebrew proof succeeds.
Findings	None	None.
Security	None	None.

How this fits together

Release closeout uses the published GitHub release and Homebrew update as inputs before reopening the changelog. The release-note extractor reads the finalized version section, which remains in place below the new heading.

flowchart LR
A[Published 0.3.8 release] --> C[Release closeout]
B[Homebrew formula update] --> C
C --> D[Unreleased heading]
D --> E[Future release notes]
F[Finalized 0.3.8 section] --> G[Release-note extractor]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep an empty Unreleased section above the finalized release notes after the publication and distribution checks complete.

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

Not applicable: this is release housekeeping, and the main-versus-branch changelog comparison directly establishes the missing heading.

Is this the best way to solve the issue?

Yes: the documented closeout calls for this heading, and the two-line addition leaves the finalized release section intact.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a two-line release-changelog closeout 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: The added heading precedes the version section consumed by the release-note extractor; this collaborator-authored changelog closeout has no contributor runtime-proof gate or stored-data contract change.

Label justifications:

• P3: This is a two-line release-changelog closeout 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: The added heading precedes the version section consumed by the release-note extractor; this collaborator-authored changelog closeout has no contributor runtime-proof gate or stored-data contract change.

Evidence

What I checked:

• Introduced change: The PR adds only the empty Unreleased heading and a blank line above 0.3.8. (CHANGELOG.md:3, 5d936fa195d4)
• Current-main gap: The current main changelog begins with the finalized 0.3.8 section and has no Unreleased heading. (CHANGELOG.md:3, ea2fb1098a2d)
• Closeout policy: The release guide directs reopening Unreleased only after GitHub and Homebrew proof succeeds. (docs/RELEASING.md:114, 5d936fa195d4)
• Release-note boundary: The extractor begins at the requested version heading, so the preceding Unreleased heading does not enter the 0.3.8 notes. (scripts/extract-release-notes.sh:14, 5d936fa195d4)
• Publication check: GitHub reports v0.3.8 published at 2026-09-24T09:17:50Z with the three documented assets; the published verifier completed successfully against the release commit. (ea2fb1098a2d)
• Homebrew update: The referenced formula commit changes the archive URL from v0.3.7 to v0.3.8 and updates its digest. (Formula/remindctl.rb:4, bb98426e21fd)

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.