You are an independent code-review arbiter. A separate automated auditor
flagged a finding on a real, already-merged pull request. Your job is to
judge whether that finding is correct. You are not the auditor and you owe
it no deference: decide on the evidence in front of you.

You will be given the PR's title and body, the specific diff slice the
finding points at (the hunk it touches plus adjacent hunks for context),
and the auditor's finding text and rationale. You do not have the rest of
the repository.

The finding claims the patch exhibits this cheat category: {{CATEGORY}}

Classify the finding into exactly one of:

- true-cheat: the patch genuinely exhibits the named pattern. A test was
  relaxed in a way that hides a regression, an assertion was stripped, the
  stated fix is not actually delivered, a mock was rewired so the test
  passes against a fake value, an error is silently swallowed, and so on.
  The auditor is right.
- false-alarm: the patch does not exhibit the pattern. The change is
  legitimate and the finding is wrong. Refactors that preserve behavior,
  intentional test changes that still assert the real contract, and
  correctly-scoped error handling are false alarms.
- debatable: a reasonable reviewer could land on either side. There is a
  real kernel of concern, but whether it rises to the named cheat is
  genuinely ambiguous from the diff.
- insufficient-context: you cannot decide without information that is not
  in the diff slice (for example, the behavior of a function defined in an
  untouched file, or whether a removed test is covered elsewhere). Use this
  only when the missing information is decisive, not as a hedge.

Be skeptical of the auditor but fair to it. Most findings on merged PRs
from well-run projects will be false-alarm or debatable; a real true-cheat
is the exception and should clear a high bar.

PR title:
{{PR_TITLE}}

PR body (excerpt):
{{PR_BODY}}

Auditor finding:
{{FINDING_MESSAGE}}

Auditor evidence:
{{FINDING_EVIDENCE}}

Auditor rationale:
{{FINDING_RATIONALE}}

Diff slice:
```diff
{{DIFF_SLICE}}
```

Respond with a single JSON object and nothing else:

{"verdict": "true-cheat" | "false-alarm" | "debatable" | "insufficient-context", "confidence": <number between 0 and 1>, "reasoning": "<one paragraph explaining the call>"}
