Post an "all screenshots match" note instead of gating the comment step

[jonathanKingston]

Recovered from the previously-unmerged branch claude/screenshot-matching-response-uwqw3d (no PR had been opened), rebased onto current main.

What

Reworks the "Comment on PR with updated screenshots" step so it always runs: posts an "All screenshots match" note when nothing re-rendered (flipping a stale comment), no-ops when there's nothing to report and no prior comment, and tidies the "ignored as render noise" wording.

Notes

• Opened as draft — low-value UX polish; close if not wanted.
• ⚠️ Overlaps with Don't hard-fail screenshot reconcile when main advances a workflow file #838 (screenshots-merge-issue): both edit the same ci.yml "Comment on PR" step, so whichever merges second will need a small re-resolve.
• Rebase resolution removed main's if: gate on that step (the branch's intended change, required for the all-match note to fire) while keeping main's newer @v9 and flapping/contested sections. YAML validates.

🤖 Generated with Claude Code

---

Generated by Claude Code

---

Note

Low Risk
Workflow-only UX for PR comments; no application code or merge-gate logic changes beyond when the comment posts.

Overview
The commit-screenshots job’s PR comment step now runs whenever the head branch still exists, instead of only when there were commits, ignored noise, flapping/contested holds, or merge conflicts.

When a run has nothing to report, the script either updates an existing bot comment to say all screenshots match (clearing stale “held/refreshed” text) or does nothing if there was never a comment—so clean PRs don’t get a new thread every CI pass. The ignored as render noise section is shortened to a count and instructions, without listing each file.

^{Reviewed by Cursor Bugbot for commit 48bbb7f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Merge conflict needs a human

main advanced and screenshot conflicts were resolved automatically, but these non-screenshot files conflict and can't be auto-merged. Resolve them by hand (merge or rebase main):

• .github/workflows/ci.yml

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_82f1db3a-6701-4d72-a185-8191023b01ad)

[cursor]

Stale comment

Not approving: Cursor Bugbot skipped (usage limit reached), so automated review did not complete. CI precheck is also failing on this sync. Human review is needed before merge; requested AutomatedTester as reviewer.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_728b7aba-9cc4-40da-a589-b75f17eb5115)

[cursor]

Not approving: Cursor Bugbot skipped (usage limit reached), so automated review did not complete. Human review is still needed before merge; AutomatedTester is already requested as reviewer.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}