pr-standards falsely flags every v2-based PR as missing a linked issue #38407

Description

The pr-standards workflow flags every PR that targets the v2 branch with needs:issue, even when the description contains a valid Closes #<number> line.

Cause: the check relies on the GraphQL closingIssuesReferences count, and GitHub only populates closing references for PRs that target the repository default branch (dev). For any other base branch the count is always 0, so the workflow labels the PR and posts the "doesn't have a linked issue" comment no matter what the description says.

Examples, all base v2, all with Closes #N in the body, all flagged: #38406, #37088, #36242, #36403.

Fix idea: when closingIssuesReferences is 0, fall back to matching the PR body against GitHub's closing keywords (close/closes/closed/fix/fixes/fixed/resolve/resolves/resolved + #number) before flagging. Happy to open a PR.

Plugins

Not applicable, repo CI workflow.

OpenCode version

Not applicable.

Steps to reproduce

1. Open a PR with base v2 and Closes #<valid issue> in the description.
2. The pr-standards job labels it needs:issue and posts the missing-issue comment.