fix(review-pr): correct OR/AND precedence in unjustified_dismissal condition

As written, the condition read: (resolved with no reply) OR (dismissive
reply AND code unchanged). This meant if someone fixed the code and
resolved the thread without commenting, Claude would still challenge them.

Fix: add parentheses so the code-unchanged guard applies to both branches:
(resolved with no reply OR dismissive reply) AND code unchanged in new diff

Caught by claude[bot] review on scality/agent-hub#26.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

Author: JBWatenbergScality

.claude/skills/review-pr/SKILL.md

@@ -60,7 +60,7 @@ gh pr diff <number> --repo <owner/repo>
 
    - **`justified`** — human reply contains substantive technical reasoning (why issue isn't applicable, acknowledged trade-off, relevant constraint) → accept silently. Add to SKIP SET. Optionally resolve thread if still open.
 
-   - **`unjustified_dismissal`** — thread resolved by human with no reply, OR reply is dismissive with no technical reasoning (`"done"`, `"ok"`, `"wontfix"` with nothing substantive) AND flagged code still unchanged in new diff → reply in thread (do NOT post new top-level comment). Add to SKIP SET.
+   - **`unjustified_dismissal`** — (thread resolved by human with no reply, OR reply is dismissive with no technical reasoning (`"done"`, `"ok"`, `"wontfix"` with nothing substantive)) AND flagged code still unchanged in new diff → reply in thread (do NOT post new top-level comment). Add to SKIP SET.
      ```bash
      gh api -X POST -H "Accept: application/vnd.github+json" "repos/<owner/repo>/pulls/<number>/comments" -f body="Issue still present in latest commit. Could you share your reasoning or clarify how it's been mitigated?<br><br>— Claude Code" -F in_reply_to=<databaseId_of_first_comment> -f commit_id="<headRefOid>"
      ```