docs(agents): say a scout verdict is a lead, not a finding

The 2026-10-19 vault de-dup campaign sent four read-only scouts over the same
pages and had to parent-verify every claim: one inverted era-page law (flagged
pages stale for documenting the retired payloads they exist to record), one
listed files that do not exist, one reported duplications grep disproved, one
cited a line past the end of the file it judged. Record the rule beside the
other evidence laws so the next agent does not integrate a yield unchecked.

Refs: vault de-dup campaign, PR #24.

AGENTS.md

@@ -942,6 +942,14 @@ linked runbooks.
   already does all three; ad-hoc fetches tend not to. Gated repos (e.g.
   `orcarouter/Qwen3.8-Flash-Next-Uncensored-GGUF`, same 104.09 GiB Q4_K_S)
   return 403 even with the host's HF token until that account accepts the gate.
+- **A scout verdict is a lead, never a finding.** In the 2026-10-19 vault de-dup
+  campaign, four read-only scouts worked the same pages: one classified era pages as
+  stale *because* they document retired payloads (that is an era page's content), one
+  reported files that do not exist, one reported duplications that grep disproved
+  (`457.9 t/s` and the ping-RTT table are solo-held by `Ethernet Bandwidth Math`),
+  and one cited a line number past the end of the file it judged. Re-verify every
+  claimed duplicate and every claimed staleness against the file and today's fleet
+  state before editing; a scout yield buys no evidence.
 
 ## Runbook Index