researchlisted

# /research — investigation whose deliverable is a decision `/task` is for changing code. This is for the issues where the output is a **recommendation** — the `RESEARCH:` issues on the APL board, "should we use X", "what is our exposure to Y". Running those through `/task` is waste: no contract to write, nothing for `gate.sh` to gate, no diff to audit or review. Two research runs done this way cost **83k and 117k tokens** and produced cited, decisive answers. The same questions through the full harness would have paid for a contract stage, an audit, a gate and a review panel, all of which would have had nothing to judge. ## Inputs An issue key (`APL-27`), a Linear URL, or a bare question. ## 1. Do not duplicate — check first ```bash "${CLAUDE_PLUGIN_ROOT}/poller/lin" issue view <KEY> ``` **Read the existing comments before doing anything.** A prior run may already have answered this: a rate limit killed an agent mid-session and its recommendation was already posted, so the relaunch produced a second contradicting comment on the same issue and a human had to reconcile them. - Substantive answer already there → **do not re-run it**. Either add only what is genuinely missing, or reply saying it already covers the ground. Say which you did. - Partial answer → extend it, naming what you are adding. - Nothing → proceed. ## 1b. Say you started, before you do anything slow ```bash "${CLAUDE_PLUGIN_ROOT}/poller/lin" issue comment list <KEY> | grep -q 'harness:<KEY>:starte