fix(#1030): use TRIGGER_ENTITY_URL for Jira forge ISSUE_URL mapping

LOCAL.md

@@ -75,7 +75,7 @@ If you're testing a new env var, export it here too. You can also use
 The issue URL above points at an issue in a separate repo (e.g.
 `your-org/test-repo`) — clone it to its own local path so `--target-repo`
 has real content to work against. The harness maps `GITHUB_ISSUE_URL`,
-`GITLAB_ISSUE_URL`, or `JIRA_ISSUE_URL` to a generic `ISSUE_URL` via the
+`GITLAB_ISSUE_URL`, or `TRIGGER_ENTITY_URL` to a generic `ISSUE_URL` via the
 per-forge env file (`env/github/*.env`, `env/gitlab/*.env`, or
 `env/jira/triage.env`):
 
@@ -130,7 +130,7 @@ Jira-specific env vars — `forge.jira` resolves natively with the current
 runner, no override workaround needed:
 
 ```bash
-export JIRA_ISSUE_URL="https://your-site.atlassian.net/browse/TESTPROJ-42"
+export TRIGGER_ENTITY_URL="https://your-site.atlassian.net/browse/TESTPROJ-42"
 export JIRA_USER_EMAIL="you@example.com"
 export JIRA_TOKEN="your-jira-api-token"
 export JIRA_BASE_URL="https://your-site.atlassian.net"

docs/triage.md

@@ -190,7 +190,7 @@ GitHub/GitLab auth vars:
 
 | Variable | Description |
 |----------|-------------|
-| `JIRA_ISSUE_URL` | The `https://<site>.atlassian.net/browse/<KEY>-<n>` URL of the issue to triage. |
+| `TRIGGER_ENTITY_URL` | The `https://<site>.atlassian.net/browse/<KEY>-<n>` URL of the issue to triage. |
 | `JIRA_USER_EMAIL` | Email address of the Jira Cloud account used for Basic auth. |
 | `JIRA_TOKEN` | API token for that account. |
 | `JIRA_BASE_URL` | Base URL of the Jira Cloud site (e.g. `https://<site>.atlassian.net`). |
@@ -225,7 +225,7 @@ If you use `base:` composition to override `harness/triage.yaml`:
 - **`ISSUE_URL` replaces `GITHUB_ISSUE_URL` inside scripts**: The sandbox and
   runner env var consumed by pre/post scripts is now `ISSUE_URL`
   (forge-neutral). `GITHUB_ISSUE_URL` (and its `GITLAB_ISSUE_URL` /
-  `JIRA_ISSUE_URL` equivalents) remain the workflow-level inputs per forge;
+  `TRIGGER_ENTITY_URL` equivalents) remain the workflow-level inputs per forge;
   the harness maps them to `ISSUE_URL` via `env.runner` / `env.sandbox`.
   Custom pre/post scripts that reference `GITHUB_ISSUE_URL` directly should
   switch to `ISSUE_URL`.

env/jira/triage.env

@@ -1,4 +1,4 @@
-export ISSUE_URL="${JIRA_ISSUE_URL}"
+export ISSUE_URL="${TRIGGER_ENTITY_URL}"
 export JIRA_USER_EMAIL="${JIRA_USER_EMAIL}"
 export JIRA_TOKEN="${JIRA_TOKEN}"
 export JIRA_BASE_URL="${JIRA_BASE_URL}"

harness/triage.yaml

@@ -97,7 +97,7 @@ forge:
         expand: true
     env:
       runner:
-        ISSUE_URL: ${JIRA_ISSUE_URL}
+        ISSUE_URL: ${TRIGGER_ENTITY_URL}
         JIRA_USER_EMAIL: ${JIRA_USER_EMAIL}
         JIRA_TOKEN: ${JIRA_TOKEN}
         JIRA_BASE_URL: ${JIRA_BASE_URL}
@@ -106,7 +106,7 @@ forge:
         JIRA_SPLIT_TRANSITION: ${JIRA_SPLIT_TRANSITION}
         FULLSEND_FORGE: jira
       sandbox:
-        ISSUE_URL: "${JIRA_ISSUE_URL}"
+        ISSUE_URL: "${TRIGGER_ENTITY_URL}"
         JIRA_USER_EMAIL: "${JIRA_USER_EMAIL}"
         JIRA_TOKEN: "${JIRA_TOKEN}"
         JIRA_BASE_URL: "${JIRA_BASE_URL}"