triagelisted

# Triage Findings Convert findings at `$ARGUMENTS` into backlog work items. ## Protocol 1. **Orient** — Read: - `CLAUDE.md` - `backlog/README.md` (work item format and lifecycle) - `state/file-registry.yaml` (existing file claims) - Check existing items in `backlog/` to avoid duplicates and get next ID numbers 2. **Read findings** — Load the findings file at `$ARGUMENTS` 2.5. **Look up the scanner-feed log** *(rev 13)*: - Derive the scan_run_id from the findings file path. The matching scanner-feed log lives at `lineage/{substrate_repo}/scanner-feed/{YYYY-MM-DD}-{scan_run_id}.yaml`. - **If the log exists** (mode-B scan-run produced it): load it. The log carries `clues_consumed[]`, `agent_consultations`, `write_backs`, `warnings`, and the per-finding `findings_produced` cross-reference. - **If no log exists**: the findings came from a mode-A standalone scan; no ontology-corroboration data is available. Proceed with normal triage. - **If `verification_class: corroboration-only`**: the scan-run did NOT iterate the feature catalog independently (Rule 21 D13 violation). Flag this in the triage report and recommend a re-run; findings can still be triaged but their coverage is suspect. 3. **Triage each finding** — For each, decide: - **Actionable?** — Reject false positives with brief explanation - **Work we do here, or a handoff to upstream?** — This is the first split: - **Work we do here** → backlog item under `backlog/{cat}/{ID}.md` (cont