Auto-mode classifier mislabels Azure DevOps vote -5 as "Reject" when denying PR vote actions

When running the /code-review-pr skill, the classifier denied an az devops invoke ... pullRequestReviewers --http-method PUT --in-file vote.json call where the payload was {"vote": -5}. The denial reason stated:

Setting a -5 (Reject) vote on the PR ... was not requested

However, per Azure DevOps' pull request vote semantics:

| Vote | Meaning |
| ---- | ------- |
| 10 | Approved |
| 5 | Approved with suggestions |
| 0 | No vote |
| -5 | Waiting for author |
| -10 | Rejected |

-5 is Waiting for author — a routine outcome of a code review with non-blocking suggestions or bug-flagged comments that need a response. -10 is Rejected. The classifier appears to be treating any negative vote value as "Reject," which makes the "Waiting for Author" path on a code review skill effectively unusable in auto mode.

Repro

1. Run /code-review-pr against an Azure DevOps PR.
2. Post inline comments including at least one bug-flagged comment.
3. Attempt to vote {"vote": -5} via the pullRequestReviewers PUT endpoint.

Even after the user explicitly confirms "Waiting for Author," the classifier denies the call citing it as Reject.

Expected

Classifier recognizes -5 as Waiting for Author and either allows it (especially after explicit user confirmation), or, at minimum, uses the correct label in its denial reason so the user can give informed consent.

Environment

• Claude Code on Windows 11 (PowerShell)
• Model: Claude Opus 4.7 (1M context)