fix: always post a review comment even with zero findings

[docker-agent]

Problem

The review-pr agent exits 0 without posting any GitHub PR comment when review_complete=true and zero findings. The review_complete=false + zero findings path explicitly says 'post a COMMENT review', but the review_complete=true path jumps to step 8 and then step 9 ('Build inline comments') — with nothing to post, the agent exits silently.

Changes

review-pr/agents/pr-review.yaml (primary fix)

• Step 5 (review_complete=true + zero findings path): now explicitly mandates posting a 🟢 APPROVE COMMENT review with an empty comments array via gh api before exiting.
• Step 8 rule rename: cagent to docker-agent-action across entire repo #4: clarified that the COMMENT event applies even when the findings list is empty — the assessment-label body must still be posted.
• "Delivering the Review" section: added a concrete zero-findings bash example with an empty comments array, giving the agent a literal template to follow.

review-pr/action.yml (defense-in-depth)

• Post-clean-summary step (EXIT_CODE=0 branch): added a check — if the verbose log exists but contains no pullrequestreview-[0-9]+ reference, post a fallback issue comment (🟢 **No issues found** — LGTM!) to guarantee PR visibility.

Testing

• All 470 existing unit tests pass (pnpm test).
• Shell tests (tests/test-job-summary.sh, tests/test-output-extraction.sh) pass.
• No changes to TypeScript source or dist/.

[docker-agent]

direction is right (the silent-exit bug was real), but the fallback comment in action.yml needs a dedup guard, otherwise every re-run stacks another LGTM on the PR. also left a couple of non-blocking notes on the agent YAML (contradictory --arg body example and ambiguous step ordering) as things to keep in mind if the zero-findings path still misbehaves after this.

[docker-agent]

issue: the fallback gh api call on line 877 posts a brand-new issues-API comment every time the workflow re-runs and the agent exits 0 without a pullrequestreview-* log entry. no dedup check at all: three re-runs = three identical 🟢 No issues found, LGTM! comments piling up.

easiest fix is embedding a sentinel marker in the body and checking for it before posting:

MARKER="<!-- docker-agent-lgtm-fallback -->"
EXISTING=$(gh api "repos/$REPOSITORY/issues/$PR_NUMBER/comments" \
  --jq "[.[] | select(.body | contains(\"docker-agent-lgtm-fallback\"))] | length")
if [ "$EXISTING" -eq 0 ]; then
  printf '%s\n🟢 **No issues found**, LGTM! [View logs](%s).' "$MARKER" "$RUN_URL" \
    | gh api "repos/$REPOSITORY/issues/$PR_NUMBER/comments" --input -
fi

(alternatively, delete-and-recreate, or just switch to gh pr review --approve which GitHub deduplicates naturally.)

[docker-agent]

Fixed in the follow-up commit (780c0a1). I used a startswith prefix match on 🟢 **No issues found** rather than an embedded HTML marker — same dedup effect, slightly simpler body. If the sentinel-marker approach is preferred for robustness (e.g. if the body text ever changes), happy to switch, but the current check covers the re-run duplicate scenario.

[docker-agent]

the startswith check works fine for this. you're right that it covers the re-run scenario, and the body is unlikely to change independently of the guard. html marker is slightly more robust against accidental body edits but not worth the extra noise here. good fix.