Target is \\u0026#34;triggering\\u0026#34; but not running in issue context, skipping update_issue\\n##[error]✗ Message 1 (update_issue) failed: Target is \\u0026#34;triggering\\u0026#34; but not running in issue context, skipping update_issue\\n\\nProcessing message 2/3: add_comment\\nResolved target issue #3 (target config: triggering)\\n✓ Message 2 (add_comment) completed successfully\\n\\nProcessing message 3/3: add_comment\\n✓ Message 3 (add_comment) completed successfully\\n\\nSuccessful: 2\\nFailed: 1\\n```\\n\\n- Child run `event`: `workflow_dispatch` (not `issue_comment`)\\n- `add_comment` resolves the triggering issue from caller context (`GH_AW_COMMENT_ID` / `aw_context`)\\n- Issue body is **not** updated\\n- Overall workflow conclusion: **failure** (“failed to deliver outputs”)\\n\\n### Expected behavior\\n\\nOn `workflow_dispatch` dispatched by centralized slash-command routing, **`update_issue` with `target: triggering` should resolve the same issue** that `add_comment` already resolves from `aw_context` (issue number, comment id, or equivalent caller payload).\\n\\nSame pattern as team membership validation, which already logs:\\n\\n```text\\nValidating centralized workflow_dispatch against originating actor \\u0026#39;\\u0026#39;\\n✓ command_name \\u0026#39;refresh-proposal\\u0026#39; resolved from workflow_dispatch aw_context\\n```\\n\\n### Impact\\n\\nFor issue-only workflows that must rewrite the issue body (e.g. freeze a submission template into a canonical section), centralized routing blocks a core safe output. Workarounds are awkward:\\n\\n- Dropping centralized routing is blocked when the same workflow also needs `issues: opened` (compiler error: cannot combine `slash_command` + `issues` without centralized strategy).\\n- Instructing the agent to use `gh issue edit` via bash bypasses safe outputs and is undesirable.\\n\\n### Suggested fix\\n\\nIn the `update_issue` handler (and likely `add_labels` / `remove_labels` with `target: triggering`), when `github.event_name === \\u0026#39;workflow_dispatch\\u0026#39;` and caller/`aw_context` includes issue context:\\n\\n1. Resolve issue number/repo from the same source `add_comment` uses today.\\n2. Apply the body/label update to that issue.\\n3. Do not require `github.event.issue` on the dispatched event.\\n\\n### Related\\n\\n- Centralized routing + `skip-bots` false negative on `github-actions[bot]` actor (repo-side workaround: removed `skip-bots`).\\n- [Agentic workflows no longer need a PAT](https://github.blog/changelog/2026-06-11-agentic-workflows-no-longer-need-a-personal-access-token/) (org-billed `GITHUB_TOKEN`; unrelated but same test setup).\\n\\n### Workaround today\\n\\nNone clean within safe outputs + centralized routing. Manual issue body edit or wait for this fix.\",\"state\":\"OPEN\",\"user\":{\"login\":\"consulthys\"},\"created_at\":\"2026-06-16T07:04:06Z\",\"updated_at\":\"2026-06-16T07:04:06Z\"}],\"totalCount\":261,\"pageInfo\":{\"hasNextPage\":true,\"hasPreviousPage\":false,\"startCursor\":\"Y3Vyc29yOnYyOpK0MjAyNi0wNi0xNlQwNzowNDowNlrPAAAAARZ3Bl0=\",\"endCursor\":\"Y3Vyc29yOnYyOpK0MjAyNi0wNi0xNlQwNzowNDowNlrPAAAAARZ3Bl0=\"}}","type":"text"}]}}}