## Summary
- Fixed `gh pr edit` commands failing with "Could not resolve to a
PullRequest" error
- When the workflow checks out a fork repository, the `gh` CLI operates
in that context and tries to find the PR in the fork instead of the
upstream repo
- Added `--repo ${{ github.repository }}` flag to all `gh pr edit`
commands to ensure they target the correct repository

## Test plan
- Create a PR from a fork with the `cc:request` label
- Verify the PR Review Responder workflow can successfully update labels

#skip-bugbot

🤖 Generated with [Claude Code](https://claude.com/claude-code)
<!-- devin-review-badge-begin -->

---

<a href="https://app.devin.ai/review/dyad-sh/dyad/pull/2338">
  <picture>
<source media="(prefers-color-scheme: dark)"
srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1">
<img
src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1"
alt="Open with Devin">
  </picture>
</a>
<!-- devin-review-badge-end -->


<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Fixes gh pr edit failures on fork-based PRs by forcing the repo context
with --repo ${{ github.repository }}. The PR Review Responder now
reliably updates cc:request/pending/done/failed labels in the upstream
repo even when the workflow runs in a fork.

<sup>Written for commit b2d37c8852965f102932662d309da8c45bf9f2f1.
Summary will update on new commits.</sup>

<!-- End of auto-generated description by cubic. -->
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>