Fix stale waiting-on-author label after maintainer-review verdict

[steipete]

Summary

A fresh ClawSweeper review can route a PR to maintainer review while leaving the older status: ⏳ waiting on author label attached.

Reproduction

Observed on steipete/CodexBar#1273:

1. An earlier review added status: ⏳ waiting on author.
2. The author addressed the actionable findings and requested several re-reviews.
3. The latest durable review says the result is ready for maintainer review and that only maintainer privacy/security approval remains.
4. The PR still retained status: ⏳ waiting on author instead of moving to status: 👀 ready for maintainer look.

CodexBar tracked the mismatch in steipete/CodexBar#1429. The stale label was corrected manually on June 11, 2026.

Expected

When the latest verdict has no contributor-facing work and routes the next action to a maintainer, remove status: ⏳ waiting on author and apply status: 👀 ready for maintainer look.

Status labels should be mutually exclusive and derived from the latest durable verdict, including re-reviews that update an existing comment.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 12, 2026, 12:05 AM ET / 04:05 UTC.

Summary
Codex review failed: retryable codex transport failure (capacity) (exit 1).

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
Review did not complete, so no work-lane recommendation was made.

Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

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

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Remaining risk / open question:

• No close action taken because the review did not complete.

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

Label changes

Label changes:

• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:needs-info: Current issue advisory state selects this label.

Evidence reviewed

What I checked:

• failure reason: retryable codex transport failure (capacity)
• codex failure detail: Codex review failed for this issue with exit 1.
• codex stderr: est/repair/live-worker-capacity.test.ts.
• codex stdout: No stdout captured.

Likely related people:

• unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)

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.