chore: prepare discrawl 0.15.6 release

[steipete]

What Problem This Solves

Seven fixes and performance improvements have landed since 0.15.5 and are ready for a patch release.

User Impact

0.15.6 makes Discord Components V2 cards searchable, accelerates exact semantic search, fixes metrics ordering and cloud publication edge cases, and refreshes the SQLite runtime and tooling.

Why This Change Was Made

Move every existing Unreleased bullet into the dated 0.15.6 section, add a concise highlight, and retain an empty Unreleased section. The official shared release workflow will publish from the verified main head after this PR lands.

Evidence

All seven release bullets and all historical changelog bullets are preserved byte-for-byte. Codex autoreview found no actionable P0–P2 findings. All 44 Go modules across the main module and optional helpers match the Go proxy's latest versions; no dependency PRs are open. The existing main CI is green. The complete documented make check gate passed on AWS Crabbox, including 86.0% coverage, race tests, vulnerability checks, and all six release snapshots. Exact-head GitHub CI is green: https://github.com/openclaw/discrawl/actions/runs/36814574406. Remote proof: https://crabbox.openclaw.ai/portal/runs/run_fc05c7e85e65d80829be1bbf2ccf170a (lease cbx_d2616bdcbace, command make check, exit 0).

[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 October 1, 2026, 12:21 AM ET / 04:21 UTC.

ClawSweeper review

What this changes

The PR groups seven existing changelog bullets into a dated 0.15.6 section, adds a search-focused highlight, and retains an empty Unreleased section.

Merge readiness

✅ Ready for maintainer review

The release preparation remains necessary: main still lists these changes as Unreleased, and v0.15.5 is the latest published release. The focused changelog patch has no actionable findings.

Priority: P3
Reviewed head: 046d1713685cf577410db10ace6d1e26a766f6b3

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct release-note patch preserves existing content and follows the documented process.
Proof confidence	🌊 off-meta tidepool	Not applicable: The changed owner is the changelog, with no runtime or stored-data contract change; ordinary contributor runtime proof is exempt under the supplied MEMBER classification.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The changed owner is the changelog, with no runtime or stored-data contract change; ordinary contributor runtime proof is exempt under the supplied MEMBER classification.
Evidence reviewed	6 items	Pinned introduced change: The complete introduced diff changes only CHANGELOG.md, adding the 0.15.6 heading and highlight and reordering existing bullets. The verified test-merge result has the same single-file scope. Release-note preservation: Read-only comparison of the pinned changelog blobs verified seven bullets in each release block, byte-identical bullet text as a multiset, and identical historical sections starting at 0.15.5. Existing release preparation contract: The release documentation explicitly directs operators to land a dated changelog section on protected main before dispatching the official workflow. The patch follows that preparation step without modifying publication code or credentials.
Findings	None	None.
Security	None	None.

How this fits together

Discrawl archives Discord messages for local search. Its changelog describes shipped changes and is included in platform archives produced by the official release workflow.

flowchart LR
 A[Changes landed on main] --> B[Unreleased notes]
 B --> C[Dated release section]
 C --> D[Official release workflow]
 D --> E[Platform archives]
 D --> F[Published release notes]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Release-note preservation	7 of 7 bullets preserved; historical sections unchanged	The release grouping retains all existing fixes and prior release notes.

Technical review

Best possible solution:

Keep the concise release notes and publish 0.15.6 through the documented official workflow after landing on main.

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

Not applicable: this PR organizes release notes; pinned-blob comparison verifies preservation of the existing content.

Is this the best way to solve the issue?

Yes: a changelog-only preparation follows the existing release process without adding another publication path.

AGENTS.md: not found in the target repository.

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

Labels

Label changes:

• add P3: This is a focused release-note preparation change with no introduced runtime behavior.
• 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 changed owner is the changelog, with no runtime or stored-data contract change; ordinary contributor runtime proof is exempt under the supplied MEMBER classification.

Label justifications:

• P3: This is a focused release-note preparation change with no introduced runtime behavior.
• 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 changed owner is the changelog, with no runtime or stored-data contract change; ordinary contributor runtime proof is exempt under the supplied MEMBER classification.

Evidence

What I checked:

• Pinned introduced change: The complete introduced diff changes only CHANGELOG.md, adding the 0.15.6 heading and highlight and reordering existing bullets. The verified test-merge result has the same single-file scope. (CHANGELOG.md:5, 046d1713685c)
• Release-note preservation: Read-only comparison of the pinned changelog blobs verified seven bullets in each release block, byte-identical bullet text as a multiset, and identical historical sections starting at 0.15.5. (CHANGELOG.md:9, 046d1713685c)
• Existing release preparation contract: The release documentation explicitly directs operators to land a dated changelog section on protected main before dispatching the official workflow. The patch follows that preparation step without modifying publication code or credentials. (docs/RELEASING.md:26, 046d1713685c)
• Current main and latest release: The pinned main changelog still has all seven bullets under Unreleased. GitHub reports v0.15.5 as the latest release, published 2026-09-20T23:53:29Z; the requested 0.15.6 preparation is therefore not already implemented there. (CHANGELOG.md:3, ef15de868972)
• Release-area routing history: Recent changelog and release-documentation history repeatedly records Peter Steinberger's work, including preparation of 0.15.5 and adoption of the unified release workflow. Deeper blame and patch inspection encountered unavailable historical blobs, so no source-line introduction attribution is claimed. (docs/RELEASING.md, ef15de868972)
• Discussion and proof scope: The supplied body describes release-note preparation rather than a runtime change; discussion contains only filtered automation comments and no human review notes. Repository State identifies the author as MEMBER, although the live pull endpoint reports CONTRIBUTOR; the supplied trusted-author classification is used for the ordinary proof exemption. (046d1713685c)

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.