Treat 404 as error: emit level=error on 404 + email+DM + feed auto-fix protocol (Elazar 404-directive, kpi-n-optimization)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-20
• wi-cli-venus commented · 2026-06-20
  SCOPED (Elazar 404-directive via generalpm relay; matches the referer-gate I flagged to Elazar). Two parts: (1) EMIT: Pluto 404s currently do NOT emit level=error → never enter the alert pipeline. not-found handler/middleware must classify + emit so 404s ride the error+fatal path (email+DM to aro:pluto live PM). (2) CLASSIFY (the anti-flood gate): route Pluto owns / internal-referrer / in-sitemap 404 → ERROR → email+DM → auto-fix autonomously IF clear+reversible (restore route / repair link / add redirect); non-reversible/destructive → block to PM/Elazar. External scanner junk-paths (/wp-login.php, /.env, /.git, stray .php, no-referrer probes) → security log (appEvents malicious/security), NOT the fix-DM — so bot spam can't bury a real dead link. Auto-fix protocol = the standing mars/venus/pluto one: clear+reversible → ship solo, report after; non-reversible/destructive → block. Related: PLUTO-157 (venus rail delivers the DM; this WI is the Pluto-app-side classify+emit). Pending Elazar veto on the carve-out.
• wi-cli-venus blocked · 2026-06-20
  Pending (1) Elazar's ruling on bot-probe 404s (no-filter vs security-log carve-out — pm-venus driving the fleet confirm; same-origin/internal-link 404=bug is settled), and (2) the venus rail delivery template + PLUTO-157 (rail delivers the DM). Internal-404 classify+emit is actionable once those land; do not dispatch coder before then.
• wi-cli-venus commented · 2026-06-20
  ALIGNED to FINAL 404 spec (pm-venus, fleet-converged): own-route/internal/sitemap/own-domain-referrer 404 → ERROR, FIRST-HIT no-threshold → DM+email+auto-fix (reversible solo, irreversible/destructive blocks); external scanner/bot probes to never-defined paths (/wp-login.php,/.env,/.git,stray .php) → SECURITY LOG only, no fix-DM; AMBIGUOUS → default to error. Implement-as-default (Elazar may veto). Still blocked on venus rail template + PLUTO-157.
• wi-cli-venus commented · 2026-06-20
  DEPENDENCY w/ PLUTO-160 (minimization cull): 404 must KEEP ip+userAgent+referrer — PLUTO-158 classification (own-route/dead-link vs external bot-probe) requires them. PLUTO-160's ip/UA drop EXCLUDES 404 for this reason. Same file surface (logger.ts + log-404 route) → implement together to avoid one WI stripping a field the other needs.