opencode: distinguish PR Review vs Issue in run-name

The run-name was hardcoded to 'Issue #N' even when the trigger was a
pull_request_review_comment (e.g. /oc review on a PR). The number is
the same in both cases (PRs are issues in GH's data model), but the
label was misleading.

Make the run-name conditional on github.event_name:
- pull_request_review_comment -> 'PR Review #N - title'
- issue_comment                -> 'Issue #N - title'

Also switched em-dash to hyphen-minus for US-ASCII safety (AGENTS.md).

Updated the orchestrator's run-title regex to match both formats:
  /(?:Issue|PR Review) #(\d+)/

so the orchestrator can still extract the issue/PR number from the
workflow_run display_title and decide whether to advance.

Author: LSantha

.github/scripts/orchestrator.js

@@ -334,10 +334,10 @@ module.exports = async ({ github, context, core }) => {
       // Fetch the display title of the completed workflow run
       const runTitle = context.payload.workflow_run.display_title || '';
 
-      // Extract issue number from display title (e.g. "Issue #469 — Add SIMD-accelerated...")
-      const match = runTitle.match(/Issue #(\d+)/);
+      // Extract issue/PR number from display title (e.g. "Issue #469 — ..." or "PR Review #471 — ...")
+      const match = runTitle.match(/(?:Issue|PR Review) #(\d+)/);
       if (!match) {
-        core.info(`Workflow run display title "${runTitle}" does not contain expected "Issue #[number]" format. Skipping.`);
+        core.info(`Workflow run display title "${runTitle}" does not contain expected "Issue #[number]" or "PR Review #[number]" format. Skipping.`);
         return;
       }
 

.github/workflows/opencode.yml

@@ -1,5 +1,5 @@
 name: opencode
-run-name: "Issue #${{ github.event.issue.number }} — ${{ github.event.issue.title }}"
+run-name: ${{ github.event_name == 'pull_request_review_comment' && format('PR Review #{0} - {1}', github.event.pull_request.number, github.event.pull_request.title) || format('Issue #{0} - {1}', github.event.issue.number, github.event.issue.title) }}
 
 on:
   issue_comment: