file-issuelisted

# File Issue (RETIRED) This skill is retired: no live code path reaches it. Two independent facts make it unreachable. GitHub Issues are disabled repo-wide on this repo (recorded as a strategy clarification dated 2026-07-16 and cited in `intentions/tactic-graph-native-dispatch.md` §4), so no issue can be created. And `dispatch-select-tick`'s legacy gh-issue-queue selection path, along with the `dispatch-select-target` and `dispatch-route` scripts, were deleted from `origin/main` by `tactic-dispatch-legacy-rewire` (PR #2869, merged 2026-07-18) — not by `tactic-legacy-router-removal`, which only records the fact (see its "What actually landed" section). So no legacy issue target is selected in the first place. Unreachable is not the same as absent. Residual `/file-issue` invocations do still appear in the repo — each inside a phase skill's legacy `TARGET_KIND=issue` lane, where the same skill's graph-native node lane already supersedes it. The list below is a snapshot of the *skill-doc* invocation sites, not a frozen inventory; regenerate it before any sweep with: ``` grep -rn '/file-issue' .claude/skills/ ``` (that grep also surfaces non-invocation mentions — dispatch script comments, `rsi-audit` test fixtures, `align` narrative prose — which are descriptive, not call sites.) - `.claude/skills/qa-fix/references/needs-main-followups.md` — Step 3.6 needs-main follow-up filing; superseded by that file's "Node-target lane" section. Its caller in the SKILL body is `.cla