chore(release): prepare v0.13.0

[vincentkoc]

Summary

• freeze the changelog for Discrawl v0.13.0 on August 3, 2026
• release the new catalog-integrity diagnostics and missing-channel annotations
• include Crawlkit v0.14.5 and the refreshed README

Validation

• git diff --check
• make tidy-check fmt
• GOLANGCI_LINT_CACHE=/tmp/discrawl-release-0-13-0-golangci-cache make lint
• make test-coverage test-race smoke
• GOWORK=off go run github.com/goreleaser/goreleaser/v2@v2.17.1 release --snapshot --clean --skip=publish
• autoreview clean

Release

After this lands, dispatch .github/workflows/release-unified.yml with version=0.13.0 from the exact protected main head.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 3, 2026, 5:44 AM ET / 09:44 UTC.

ClawSweeper review

What this changes

This PR changes the CHANGELOG.md heading from Unreleased to 0.13.0 - 2026-08-03 to prepare the next Discrawl release.

Merge readiness

⚠️ Ready for maintainer review - 1 item remains

Keep this draft open. It is a maintainer-authored, release-owned changelog freeze that matches the current unreleased content and the repository’s unified release flow; it needs normal release-owner timing and final check completion, not automated cleanup.

Priority: P3
Reviewed head: 207d680c6bd69d772fc2162fe5e2b04c22f46fa7

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused and correct release metadata patch with appropriate release validation listed in the PR body.
Proof confidence	🌊 off-meta tidepool	Not applicable: This maintainer-authored release metadata-only patch does not alter a runtime path requiring external real-behavior proof.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This maintainer-authored release metadata-only patch does not alter a runtime path requiring external real-behavior proof.
Evidence reviewed	5 items	Current release notes: Current main keeps the catalog-integrity diagnostics, Crawlkit v0.14.5 update, and README refresh under Unreleased, matching the three items named in this PR body. Exact proposed patch: The branch is a direct child of current main and changes only CHANGELOG.md, replacing the unreleased heading with the intended version and date. Release workflow: The unified workflow requires a version input and packages CHANGELOG.md, LICENSE, and README.md with the signed release artifacts.
Findings	None	None.
Security	None	None.

How this fits together

Discrawl’s release workflow accepts an explicit version from protected main, then produces signed release artifacts. CHANGELOG.md is included in those artifacts, so this change supplies the user-visible release heading for that publication.

flowchart LR
  A[Protected main commit] --> B[Release preparation PR]
  B --> C[Release-owned changelog]
  C --> D[Unified release workflow]
  D --> E[Signed release artifacts]
  E --> F[GitHub release]

Loading

Before merge

• Complete next step (P2) - This member-authored draft requires a release owner to choose the final merge and workflow-dispatch moment; it is not an automated repair candidate.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Release metadata diff	1 file affected; 1 line changed	This branch only freezes the release heading; runtime behavior and artifact-building code are unchanged.

Technical review

Best possible solution:

Merge the version freeze only when the intended protected main head is ready to publish, then dispatch the unified release workflow with 0.13.0 so it creates the tag and signed artifacts from that exact commit.

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

Not applicable: this PR changes release metadata only, not a runtime behavior with a reproduction path.

Is this the best way to solve the issue?

Yes. Updating only the release-owned changelog heading is the narrow established release-preparation path, provided the release owner confirms the final protected main head before dispatch.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add P3: This is a narrow release-maintenance change with no reported user-facing regression or runtime impact.
• 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 maintainer-authored release metadata-only patch does not alter a runtime path requiring external real-behavior proof.

Label justifications:

• P3: This is a narrow release-maintenance change with no reported user-facing regression or runtime impact.
• 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 maintainer-authored release metadata-only patch does not alter a runtime path requiring external real-behavior proof.

Evidence

What I checked:

• Current release notes: Current main keeps the catalog-integrity diagnostics, Crawlkit v0.14.5 update, and README refresh under Unreleased, matching the three items named in this PR body. (CHANGELOG.md:3, cfe1506d5de6)
• Exact proposed patch: The branch is a direct child of current main and changes only CHANGELOG.md, replacing the unreleased heading with the intended version and date. (CHANGELOG.md:3, 207d680c6bd6)
• Release workflow: The unified workflow requires a version input and packages CHANGELOG.md, LICENSE, and README.md with the signed release artifacts. (.github/workflows/release-unified.yml:4, 762f10c51f83)
• Prior release provenance: The v0.12.0 annotated release tag resolves to the commit that introduced unified-release tag ownership and is contained in current main, establishing the release mechanism this PR follows. (.github/workflows/release-unified.yml:21, 762f10c51f83)
• Repository review policy: The applicable repository policy treats OpenClaw changelogs as release-owned and says normal contributor, repair, and automerge lanes should not be asked to edit them. (../AGENTS.md:44)

Likely related people:

• vincentkoc: Authored this release-preparation commit and the immediately preceding current-main Crawlkit release-note update. (role: recent release-area contributor; confidence: high; commits: 207d680c6bd6, cfe1506d5de6; files: CHANGELOG.md)
• Peter Steinberger: Authored the current unified-release workflow migration that the v0.12.0 tag and this proposed v0.13.0 process use. (role: release-workflow introducer; confidence: high; commits: 762f10c51f83; files: .github/workflows/release-unified.yml)
• github-actions[bot]: Authored the recent release correction that reopened the changelog after the v0.12.0 release. (role: recent release-flow contributor; confidence: medium; commits: f5074c9bf61f; files: CHANGELOG.md)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Complete the running release-check and test jobs, then confirm the exact protected main SHA before dispatching the unified release workflow.

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.