Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed May 30, 2026, 5:29 PM ET / 21:29 UTC.

Summary
Keep open: the current README still shows a failing Release workflow badge even though recent tag-push release runs succeeded, so this is a valid narrow docs cleanup.

Reproducibility: yes. Current main's README badge SVG reports release - failing, while the event-scoped push badge reports passing and the latest tag-push release run succeeded.

Next step
This is a narrow, reproducible README-only repair with a clear one-line likely fix and no product decision blocker.

Review details

Best possible solution:

Update the README Release badge URL to reflect tag-push release status, likely by adding ?event=push, while leaving the working release workflow unchanged.

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

Yes. Current main's README badge SVG reports release - failing, while the event-scoped push badge reports passing and the latest tag-push release run succeeded.

Is this the best way to solve the issue?

Yes. The narrow maintainable fix is a README badge URL change; the workflow already releases successfully and does not need behavior changes.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 9a42efcdaefc.

Label changes

Label changes:

add P3: This is a low-risk README badge accuracy issue with no runtime or release-flow breakage.
add issue-rating: 🦀 challenger crab: Current issue advisory state selects this label.
add clawsweeper:current-main-repro: Current issue advisory state selects this label.
add clawsweeper:queueable-fix: Current issue advisory state selects this label.
add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.

Label justifications:

P3: This is a low-risk README badge accuracy issue with no runtime or release-flow breakage.

Evidence reviewed

Acceptance criteria:

rg -n "actions/workflows/release.yml/badge.svg" README.md
curl -L -s 'https://github.com/openclaw/crabbox/actions/workflows/release.yml/badge.svg?event=push' | sed -n 's/.<title>([^<])</title>.*/\1/p'

What I checked:

Current README badge is unscoped: README.md line 6 uses the release workflow badge URL without an event or branch query, so it currently renders the default failing badge. (README.md:6, 9a42efcdaefc)
Badge failure reproduced: Fetching the current badge SVG returns a title of release - failing; fetching the same workflow badge with ?event=push returns release - passing.
Release flow itself recently succeeded: The latest tag-push release workflow run for v0.23.0 completed successfully, while the only main-branch workflow_dispatch run is cancelled and appears to be what the unscoped badge is reflecting.
Release workflow is tag-push oriented: The release workflow triggers on push tags matching v* plus manual dispatch, which supports scoping the badge to push release runs instead of the cancelled main dispatch state. (.github/workflows/release.yml:3, 9a42efcdaefc)
No canonical duplicate found: Searches for release badge and README badge found this issue as the only direct open match and no open PR taking ownership of the fix.

Likely related people:

steipete: The current README badge lines and release workflow surface are blamed to the v0.23.0 release commit, and the recent successful release run was triggered by the same GitHub actor. (role: recent area contributor; confidence: high; commits: e35b7a78d5bb, 9a42efcdaefc; files: README.md, .github/workflows/release.yml, CHANGELOG.md)

How this review workflow works

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.

The README's badge of release is red, even though the release flow works. #189

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions