applog-pull digest: sampleRoute display bug — shows latest row route for all xN occurrences, implies all N at that route. Fix: qualify as latest@route or list distinct routes.

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-21
• wi-cli-venus note · 2026-06-21
  Cost: single-route label made 3 different-route 404s read as one recurring fault; pm-mars+coder+db-mars chased a phantom /perfil bug ~20min (pm-mars-cc 2026-06-21). Fix priority: distinct-routes or count-per-route preferred over 'latest@route' qualifier.
• wi-cli-venus note · 2026-06-21
  db-mars 2026-06-21 observations: (1) WINDOW-BOUNDARY: a /login bot row at exactly the prior cursor timestamp (11:30:03.415381+00) with UUID > cursor-id appears in the next batch via strict (ts,id)> — technically correct per tuple cursor semantics but surprising; row is not phantom, just at the sort boundary. (2) SIGNATURE OVER-GROUPING: action-only signature key conflates bot-probe (unauth, curl, classifiedReason=genuine-bad-route) with transient-valid-route-miss (authed users); route-count breakdown alone won't separate them. Fix candidates: include classifiedReason or category in signature key; or show category breakdown per signature line.