/pr auto misses review threads

### Describe the bug

❯ Okay so there aren't any unresolved threads?

● I’ll verify the review thread state directly.

● Check PR review thread resolution state (shell)
│ gh api graphql -f query='query { repository(owner:"AylaLegal", name:"Ayla") { pullRequest(number: 80) { reviewThreads(first: 100) { nodes { isResolved isOutdated path
│ comments(first: 20) { nodes { author { login } body } } } } } } }' 2>&1
└ 2 lines...

● Actually yes — 2 unresolved threads remain.

### Affected version

1.0.63

### Steps to reproduce the behavior

Run /pr auto against a PR with an open review thread

### Expected behavior

It should know to query the review threads and address them

### Additional context

MacOS
GPT-5.4-xhigh

Start by reproducing /pr auto against a pull request with an open review thread, then inspect the GitHub GraphQL reviewThreads query shown in the issue. Trace how /pr auto determines remaining review work and ensure unresolved threads are included in that process. Done means the command detects and addresses open review threads, including the reported case with two unresolved threads.

Written by the indexing model from the issue text.