fix: improve issue URL format in firewall-issue-dispatcher prompt (#1899)

Agent-Logs-Url: https://github.com/github/gh-aw-firewall/sessions/3169bf2f-5258-452f-8a24-255e8067b4c1

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: Landon Cox <landon.cox@microsoft.com>

Author: 3 people

.github/workflows/firewall-issue-dispatcher.lock.yml

@@ -65,23 +65,21 @@ gh api graphql -f query='
 
 ## Step 2: Filter Locally
 
-From the response, filter out issues where **any comment** contains `github.com/github/gh-aw-firewall/issues/`. These are already audited. Do this filtering in your analysis — do NOT make additional API calls.
+For each issue found, read its comments and check whether any comment contains a reference to a `github/gh-aw-firewall` issue (i.e., a URL matching `https://github.com/github/gh-aw-firewall/issues/` or a GitHub cross-repo reference matching `github/gh-aw-firewall#`). If such a comment exists, **skip** that issue — it has already been audited.
 
 If no unprocessed issues remain, call `noop` and stop.
 
 ## Step 3: Create Tracking Issues
 
 For each **unprocessed** issue:
 
-1. **Create a tracking issue in `github/gh-aw-firewall`** with:
-   - Title: `[awf] <component>: <summary>`
-   - Body: **Problem**, **Context** (link to original), **Root Cause**, **Proposed Solution**
-   - Reference specific source files. See `AGENTS.md` for component descriptions.
+4. **Comment on the original `github/gh-aw` issue** linking to the newly created tracking issue. Use this exact format:
 
-2. **Comment on the original `github/gh-aw` issue**:
-   > 🔗 AWF tracking issue: https://github.com/github/gh-aw-firewall/issues/NUMBER
+   > 🔗 AWF tracking issue: https://github.com/github/gh-aw-firewall/issues/{NUMBER}
 
-## Step 4: Summarize
+   where `{NUMBER}` is replaced with **only the numeric issue number** (e.g., `1896`). Do NOT include the repository name, hash symbols, or any other text — just the number in the URL path. Use the `add_comment` safe output tool with `repo: "github/gh-aw"` and the original issue number.
+
+### 4. Report Results
 
 Report: issues found, skipped (already audited), tracking issues created.