docs: prepare 0.3.6 release notes

[steipete]

Collect the complete 0.3.6 Unreleased notes after the v0.3.5 release: clearer notification-alarm guidance (#80) and the repaired Homebrew verifier handoff (#81). Both implementation branches are independent of main and intentionally leave CHANGELOG.md untouched. Land this PR last.

Recommend patch 0.3.6. This PR does not bump version files, create a tag, or publish a release. Commander 0.2.4 and all referenced GitHub Actions release lines are current; pnpm reports no outdated dependencies and its lockfile has no dependency entries.

Validation: changelog-only diff, existing released sections unchanged, P2 autoreview clean. Implementation proof is on #80 and #81; exact-head CI is required on all three PRs and on merged main before release preparation.

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

[steipete]

Verified head 899ff98276469400729db6072709777a86d3fa67: CHANGELOG.md is the only changed file, there is exactly one Unreleased section, and every released section is byte-identical to tag v0.3.5. P2 autoreview is clean for the committed branch against origin/main.

The two bullets cover every prepared user-visible change since v0.3.5. Built-CLI proof and 92 passing tests (93.8% core coverage) are recorded on #80; live published-verifier proof and the complete release harness are recorded on #81. Commander and the referenced GitHub Actions lines are current; there are no npm dependencies to refresh.

Land #80 and #81 before this PR. Recommend patch 0.3.6; tagging, signing/notarization, publishing, native release verification, and Homebrew publication remain release-time gates.

[clawsweeper]

Codex review: blocked before merge. Reviewed September 7, 2026, 5:16 AM ET / 09:16 UTC.

ClawSweeper review

What this changes

Adds Unreleased highlights and two release-note entries covering notification-alarm guidance and the Homebrew verifier handoff.

Merge readiness

⛔ Blocked before merge - 2 items remain

Keep open: these release notes are absent from the reviewed main revision and coherently cover two pending implementation PRs. No actionable patch defect was found; the collaborator-authored PR is also protected from automatic closure.

Priority: P3
Reviewed head: 899ff98276469400729db6072709777a86d3fa67

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, accurate preparatory notes patch with no correctness findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: This collaborator-authored PR changes only changelog prose; runtime proof belongs to the linked implementation reviews.
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 PR changes only changelog prose; runtime proof belongs to the linked implementation reviews.
Evidence reviewed	6 items	Exact introduced change: The complete pinned diff adds five lines to the Unreleased section only; existing released sections remain unchanged. Main has an empty Unreleased section. Explicit implementation dependencies: The supplied PR body says to land these notes last. #80 supplies the alarm-help clarification and #81 supplies bare workflow-path acceptance; both are open in the captured GitHub context. Their described changes match the two entries. Release preparation contract: The release guide separates finalized notes and synchronized versions from subsequent tagging and publishing. It expressly permits release-harness work while notes remain Unreleased, so this preparatory PR need not bump versions.
Findings	None	None.
Security	None	None.

How this fits together

remindctl’s changelog records user-facing changes for its macOS Reminders CLI. Release tooling extracts a finalized version section for GitHub release notes.

flowchart LR
 A[Implementation changes] --> B[Unreleased changelog]
 B --> C[Finalize version section]
 C --> D[Release note extraction]
 D --> E[GitHub release notes]

Loading

Before merge

• Resolve merge risk (P1) - The notes describe two changes still pending in the captured GitHub context; their final wording depends on what those implementation PRs land.
• Complete next step (P2) - Land fix: clarify notification alarms and native Urgent #80 and fix: accept GitHub release verifier workflow paths #81 first, then confirm these notes match their final implementations.

Agent review details

Security

None.

Review metrics

None.

Merge-risk options

Maintainer options:

1. Decide the mitigation before merge
   Keep the concise Unreleased entries synchronized with the landed implementations, then finalize the version through the documented release process.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Technical review

Best possible solution:

Keep the concise Unreleased entries synchronized with the landed implementations, then finalize the version through the documented release process.

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

Not applicable: this PR changes release-note prose only; its exact five-line delta was inspected.

Is this the best way to solve the issue?

Yes: a separate final notes PR matches the stated landing sequence and existing release process without mixing versioning or publication into the change.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a bounded release-documentation update with no runtime or workflow changes.
• 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 a bounded release-documentation update with no runtime or workflow changes.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Evidence

What I checked:

• Exact introduced change: The complete pinned diff adds five lines to the Unreleased section only; existing released sections remain unchanged. Main has an empty Unreleased section. (CHANGELOG.md:5, 899ff9827646)
• Explicit implementation dependencies: The supplied PR body says to land these notes last. fix: clarify notification alarms and native Urgent #80 supplies the alarm-help clarification and fix: accept GitHub release verifier workflow paths #81 supplies bare workflow-path acceptance; both are open in the captured GitHub context. Their described changes match the two entries.
• Release preparation contract: The release guide separates finalized notes and synchronized versions from subsequent tagging and publishing. It expressly permits release-harness work while notes remain Unreleased, so this preparatory PR need not bump versions. (docs/RELEASING.md:24, 899ff9827646)
• Current implementation boundary: The inspected main-equivalent command files still describe alarms as 'Alarm date' and 'Set alarm date'; the verifier still accepts only the default-branch-qualified workflow path. These pending implementation changes are not part of this changelog-only patch. (scripts/require-published-verifier.sh, 899ff9827646)
• Release history and routing: Available history identifies Peter Steinberger on the main commit opening the Unreleased section and the preceding v0.3.5 release commit. The supplied latest-release metadata also identifies v0.3.5. Detailed historical show/blame attempts could not load an older missing blob because remote DNS resolution failed; no source-line introduction claim is made. (CHANGELOG.md:3, b366b1449e63)
• Repository policy and cleanliness: The root AGENTS.md and .agents directory are absent, and the tracked tree contains no AGENTS.md. The whitespace check passed and the final working-tree status was clean. (899ff9827646)

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.