refactor(#1053): replace TRIGGER_ENTITY_URL with FULLSEND_WORK_ITEM_URL

[fullsend-ai-coder]

Summary

• Replaces all occurrences of TRIGGER_ENTITY_URL with FULLSEND_WORK_ITEM_URL across the codebase, aligning with the decision in chore(dispatch): provide FULLSEND_WORK_ITEM_URL in addition to GITHUB_ISSUE_URL fullsend#6611.
• Updated files: harness/triage.yaml (Jira forge runner and sandbox env), env/jira/triage.env, docs/triage.md (Jira setup table and migration notes), and LOCAL.md (local testing guide).

Testing

• All triage-related shell script tests pass (pre-triage-test.sh, post-triage-test.sh).
• check-bundle confirms bundled scripts are consistent.
• No test scripts referenced the old variable name — the rename is purely in configuration and documentation.

---

Closes #1053

Post-script verification

• Branch is not main/master (agent/1053-replace-trigger-entity-url)
• Secret scan passed (gitleaks — 2fbb7da338097ad4c3d659820444c7523a0f1e63..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:24 PM UTC · Completed 8:36 PM UTC

Commit: 975ce4b · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.58

[fullsend-ai-review]

Risk Assessment: moderate (2/5)

Details

Straightforward env-var rename across 4 config/doc files by a known bot; minimal change size and perfect issue-scope alignment keep risk low, but moderate historical churn and fix-commit density on the touched files nudge the composite to moderate.

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] harness/triage.yaml — This PR modifies harness/triage.yaml, which is under a protected path (harness/). The PR links to issue Replace TRIGGER_ENTITY_URL with FULLSEND_WORK_ITEM_URL #1053 and the description explains the rationale (variable rename per upstream decision in chore(dispatch): provide FULLSEND_WORK_ITEM_URL in addition to GITHUB_ISSUE_URL fullsend#6611). Human approval is always required for protected-path changes, regardless of context.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 9:21 PM UTC · Completed 9:34 PM UTC

Commit: 975ce4b · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $5.53

[fullsend-ai-retro]

Retro: PR #1054 — Replace TRIGGER_ENTITY_URL with FULLSEND_WORK_ITEM_URL

Timeline

Time (UTC)	Event
20:14:25	Issue #1053 opened by ralphbean
20:14:28	Triage agent dispatched (run 33009396141)
20:14:31	/fs-code command posted
20:14:35	Code agent dispatched (run 33009405532)
20:20:28	Triage agent completes — identifies 3 affected files
20:21:09	Code agent completes (3m42s, $2.22) — finds and changes 4 files
20:22:03	PR #1054 created
20:22:07	Review agent dispatched (run 33010039535)
20:25:51	Human approves PR
20:36:20	Review agent completes (14 min, $2.58) — posts risk assessment (moderate 2/5) and one protected-path finding
20:47:47	Functional tests pass (after ok-to-test label applied)
21:19:10	PR merged

Workflow quality

Code agent: Excellent. Completed a clean 7-line rename across 4 files in under 4 minutes, passed all pre-commit hooks, and required zero rework. Notably, the code agent found an additional file (env/jira/triage.env) that the triage agent's analysis missed.

Triage agent: Completed quickly but its affected-files analysis was incomplete — it listed 3 files (6 occurrences) but missed env/jira/triage.env (1 occurrence). The triage agent's proposed verification command scoped its grep to specific directories (harness/, docs/, LOCAL.md) rather than searching the full repository, which is why the env/ directory was overlooked.

Review agent: Ran correctly and produced accurate findings. The sole posted finding (protected-path flag on harness/triage.yaml) was valid. The risk assessment (moderate 2/5) provided useful context. The review agent internally generated 18 findings but filtered to 1, showing effective noise reduction.

Functional tests: Two intermediate failures on label events (risk/moderate, requires-manual-review) were expected fail-closed behavior — no tests actually ran in those cases. Tests passed once ok-to-test was applied.

Evidence for existing issues

• Code agent should extract and verify structured requirements from issue body when triage criteria are thin #1012 (code agent should compensate for thin triage output): This retro provides a concrete example — the triage agent's file-scope analysis missed env/jira/triage.env, and the code agent independently found it by searching the full repo. The code agent's compensation worked perfectly here, but the triage gap could mislead agents that rely on triage output for scoping.

Proposals filed

• Triage agent file-scope analysis should use repo-wide search for rename/replace tasks (in fullsend-ai/agents)