404 classifier mis-routes bot-probe paths (.env harvest) as [warn] operator DMs - should be security-log-only per Elazar 2026-06-20 rule

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-22
• wi-cli-venus completed · 2026-06-22
  PASS:a78c9be v1.76.4. Root cause was downstream of the existing SCANNER_PATH_RE matcher: security-classified bot-probe 404s persisted at level=warn/category=navigation, and the EVO-16 alert daemon keys on level=warn -> paged Elazar. Fix (not-found-log.ts, 1-file): isBotProbe=tier.category===security branch persists level=info/category=malicious/forceSync=true -> sits below the warn paging threshold, retains in security category. Genuine 404s unchanged (warn/navigation). Audit PTD clean: build READY, 0 runtime errors, 1.76.4 live+alias-matched, acceptance probes correct, no double-writes.