chore: prepare v0.8.6 release

[steipete]

Prepare v0.8.6 by converting the existing Unreleased heading to a dated release section. Preserve all three credited fixes and the maintenance notes verbatim so the unified release workflow can extract its required changelog section.

Validated with the shared workflow's exact release-notes extractor, git diff --check, and Codex autoreview (no actionable findings).

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 31, 2026, 4:38 AM ET / 08:38 UTC.

ClawSweeper review

What this changes

Changes the top changelog heading from Unreleased to the dated v0.8.6 release section while retaining all existing notes.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep open. This is a focused collaborator-authored release-preparation PR; its one-line changelog change is consistent with the repository’s documented unified release flow and has no actionable correctness finding.

Priority: P3
Reviewed head: c004efb13f148161de40131c198ae487c97fea9a

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused release-maintenance patch with a clear established pattern and no identified defect.
Proof confidence	🌊 off-meta tidepool	Not applicable: Not applicable: this collaborator-authored release-note preparation changes no executable product behavior; the PR body reports targeted release-note extraction validation.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: Not applicable: this collaborator-authored release-note preparation changes no executable product behavior; the PR body reports targeted release-note extraction validation.
Evidence reviewed	5 items	Focused introduced change: The verified PR delta changes only the top-level heading to a dated v0.8.6 section; the three fix credits and maintenance entry remain intact. Current release-note content: The resulting section contains the intended v0.8.6 heading followed by the existing fixes and maintenance notes. Release workflow contract: The contribution guide identifies the manual unified workflow as the official release path and says it creates the version tag and publishes independently verified release bytes.
Findings	None	None.
Security	None	None.

How this fits together

Slacrawl’s changelog supplies the release notes consumed by the manual unified release workflow. The workflow turns the dated section into the published version’s release material and assets.

flowchart LR
  A[Completed fixes] --> B[Changelog section]
  B --> C[Release preparation PR]
  C --> D[Unified release workflow]
  D --> E[Versioned release assets]

Loading

Before merge

• Complete next step (P2) - No concrete repair is identified; this focused collaborator release-preparation change should proceed through normal review and checks.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Release-note scope	1 heading changed; 0 release-note entries altered	The narrow diff preserves the credited fixes and maintenance notes intended for the release.

Technical review

Best possible solution:

Merge the dated release-note section once the normal release checks confirm it remains extractable by the unified workflow.

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

Not applicable. This PR changes release-note metadata rather than a user-facing runtime behavior.

Is this the best way to solve the issue?

Yes. A dated top-level changelog section matches the documented unified release workflow and the prior v0.8.5 release-preparation pattern.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a low-risk release-note maintenance change with no product 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: Not applicable: this collaborator-authored release-note preparation changes no executable product behavior; the PR body reports targeted release-note extraction validation.

Label justifications:

• P3: This is a low-risk release-note maintenance change with no product 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: Not applicable: this collaborator-authored release-note preparation changes no executable product behavior; the PR body reports targeted release-note extraction validation.

Evidence

What I checked:

• Focused introduced change: The verified PR delta changes only the top-level heading to a dated v0.8.6 section; the three fix credits and maintenance entry remain intact. (CHANGELOG.md:3, c004efb13f14)
• Current release-note content: The resulting section contains the intended v0.8.6 heading followed by the existing fixes and maintenance notes. (CHANGELOG.md:3, c004efb13f14)
• Release workflow contract: The contribution guide identifies the manual unified workflow as the official release path and says it creates the version tag and publishes independently verified release bytes. (CONTRIBUTING.md:52, c004efb13f14)
• Release-history precedent: Recent changelog history includes the prior v0.8.5 release-preparation commit by the same current-main release contributor. (CHANGELOG.md:15, b793612bfa8a)
• Whitespace validation: The introduced changelog patch has no whitespace errors. (CHANGELOG.md:3, c004efb13f14)

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.