scanlisted

# Run Scanner Execute the audit scanner at `$ARGUMENTS`. ## Protocol 1. **Orient** — Read these files (do NOT skip): - `CLAUDE.md` (system overview — nine-gate Quality Bar and Gate 9 Source-of-Truth table) - `navigation/features.yaml` (feature index) - `navigation/architecture.md` (integration-pattern + canonical-repo map; every repo name encountered during the scan is classified against this file) - The relevant `navigation/domains/*.md` for the scanner's target domain 2. **Load scanner definition** at `$ARGUMENTS`. Extract: - Target repo and scope - Method (step-by-step) - Criteria (what counts as a finding) - Output format - Chunking strategy (if applicable) - **`ontology_feed:` block (if present)** — determines run mode (see step 2.5) 2.5. **Determine run mode** *(rev 13)*: - **If `ontology_feed:` is absent OR `ontology_feed.enabled: false`** → **Mode A (standalone)**. Continue with steps 3-10 unchanged. This is backward-compatible — every existing scanner runs as before. - **If `ontology_feed.enabled: true`** → **Mode B (ontology-fed)**. Execute mode B sub-protocol below before continuing to step 3. Mode is LOCKED for the run — never switched mid-session. ### Mode B sub-protocol *(rev 13, per APPROACH.md §20 + scanners/README.md "Ontology-fed mode")* 2.5.1. **Substrate-presence check**: verify `lineage/{substrate_repo}/` exists with `manifest.yaml`, `nodes.jsonl`, `feature-flows/index.yaml`. If ANY is missing → ABORT wi