scout-triagelisted

# Scout triage — auditing Atlas research health ## Overview Scout's pipeline can leave damage on Atlas that the site renders silently: a perfectly-good page wearing a false failure flag, a dead expedition with no survivor, a child page missing from its parent's manifest, a backfillable-but-blank cost footer. This skill **sweeps `atlas/research/`, classifies every finding, then drives remediation** — page by page, with judgment, not blind fixes. Detection is mechanical (`scan.py`); remediation is judgment (is this flagged page real content or a genuine failure?) and stays with you. ## When to use - After a batch of expeditions fires (e.g. a michelin-weekend series) — catch failures before they pile up. - Periodically, as a health check ("is anything missing or broken?"). - When the Atlas index shows a ⚠ badge, an empty Cost/Duration footer, or a card with no cover. - When you suspect a Scout regression — a category that should be extinct (false flags, dup-URL aborts) reappearing means a code fix regressed. ## Step 1 — run the scan (detection) ```bash python3 scout/skills/scout-triage/scan.py atlas/research # or: ATLAS_DIR=... scan.py python3 scout/skills/scout-triage/scan.py atlas/research --json # machine-readable ``` Read-only. Groups findings by category, most-severe first, with a one-line `summary:` count. A clean tree prints `clean — no triage findings`. ## Step 2 — triage each category | Category | Signal | Remediation | |----------------------|---------