PLUTO-3 ·
plutoEvents-table hygiene review (last 24h): labeling correctness, keep-vs-drop per event type, recent-events view
- Ref
PLUTO-3(#746)- Project
pluto- Status
- done
- Priority
- normal
- Type
- chore
- Assigned
- coder-pluto-cc
- Created by
- wi-cli-venus
- Created
- 2026-06-06T19:33:10.942Z
- Updated
- 2026-06-06T20:04:40.550Z
- Closed
- 2026-06-06T20:04:40.550Z
Questions
No questions.
Event log
-
Brainstorm complete, report delivered to Elazar. Findings: (1) commons doc drift — appEvents is level(error|warn|info)+category+action, not eventType error|auth|info. (2) 9 import* breadcrumbs mislabeled level=error via logClientCaughtError (alumnos-import.tsx) — papered over at view layer (vAppErrorsRecent NOT LIKE import%) not source. (3) 4 business-CUD events duplicate row/archive history (approveAccessRequest, completarAsignacion, accessRequestInfoProvided, accessRequestCreated) — banned; keep email/cron/auth/caught-error telemetry. (4) category=NULL on most rows. (5) 7 appEvents views: vAppErrorsRecent already a 24h deduped error view; 6 redundant LIMIT-N views = sprawl; missing semantic all-levels 24h view. researcher: OWASP taxonomy expansion + prune-by-category retention. BLOCKED on Elazar decisions: greenlight steps1-5? OWASP expansion now/defer? route commons fix to bin-whey-cc?
-
Greenlit by Elazar. Source-side label hygiene → coder.
-
coder-pluto-cc
-
Shipped d04b8f0 v1.64.0, audit PTD PASS. Label hygiene: log-categories.ts SSOT (moved out of use-server logger.ts, fixed /auth/callback build break), logClientInfo + logAuthz helpers, dropped 11 import success-breadcrumbs (kept genuine client errors), removed 4 business-CUD events, categories wired (authz/auth/email/cron/navigation, default system).