Redirect-overfire phantom 404s page Elazar via the live EVO-16 real-time rail (false / and /mi-cursada 404s)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-21
• wi-cli-venus commented · 2026-06-21
  Surfaced 2026-06-21 by the now-live EVO-16 real-time alert rail (NOTIFYs on warn). Two phantom page_not_found warns reached PM+Elazar real-time: id d0d5ce87 (route /) + 790b2e2b (/mi-cursada), 11:45:49Z ~0.8s apart, identical fingerprint. Audit read-only triage (audit-pluto-cc-mqnq2ixl9epb): classifiedReason=unknown (resolves to a valid current template → conceptual routeResolves=TRUE), tierCategory=navigation, tierLevel=error UNCAPPED, persisted level=warn (NOTFOUND_PAGING_ENABLED off), alert=false, softNav=FALSE secFetchDest=document (hard loads, NOT deploy-skew), referrer=https://campusgrado.odontologia.uba.ar/ (external UBA campus portal), isAuthenticated=true viewerRoles=[alumno]. Reading: one authenticated alumno followed an external campus-portal link into / (role-aware redirector) and /mi-cursada; not-found.tsx rendered during the redirect() resolve on both VALID routes -> 2 phantom rows. Benign + known (PLUTO-165/169 redirect-overfire), NO regression today. ISSUE: because EVO-16 lowered the rail to warn and these phantoms carry tierLevel=error/classifiedReason=unknown, every external-referer hard-load into a redirector route now pages PM+Elazar as a FALSE homepage/route 404 -> recurring false-alarm noise on the channel Elazar explicitly watches (campus-portal arrivals are a normal alumno flow). DURABLE FIX (audit's rec, not a tier change): apply the PLUTO-169 resolve-gate to SUPPRESS the phantom AT CAPTURE when matchesAnyRouteTemplate=TRUE, so resolve=TRUE rows never write/page. Low pri; revisit if phantom volume on the rail becomes noticeable or if Elazar flags the false pages. Do NOT start without PM/Elazar go.
• wi-cli-venus commented · 2026-06-21
  Recurrence confirmed same session: +4 page_not_found @/mi-cursada in the 08:50Z pm-only digest (kind=alert), on top of the 2 real-time rows at 11:45:49Z. ~6 phantoms in minutes = the predicted recurring redirect-overfire noise. MITIGATION ALREADY IN PLACE: the real-time rail's 10min-per-route dedup collapse-with-count caps Elazar's kind=dm pages at 1/route/10min, so his actual exposure is ~1 /mi-cursada page, NOT the collapsed 4 (the digest is pm-only/UI-hidden). So this is bounded noise, not a flood -> stays LOW pri. Durable fix unchanged (PLUTO-169 resolve-gate at capture). Re-evaluate priority only if dedup proves insufficient or Elazar flags the page.
• wi-cli-venus commented · 2026-06-21
  Subsumed by PLUTO-180 (EVO-12 two-sink fix). The redirect-overfire is one manifestation of the broader every-render not-found-boundary capture; pulling capture out of the boundary (PLUTO-180) cures the redirect-resolve phantom too. Will close PLUTO-179 when PLUTO-180 ships + PTD-passes.
• wi-cli-venus completed · 2026-06-21
  Subsumed by PLUTO-180 — the two-sink removes the capturing not-found boundary entirely, eliminating the redirect-overfire source. No separate fix needed.