Sub-ticket of PLUTO-186 prod LOG_LEVEL is >=3 (audit found during PLUTO-184 PTD; code default is 1) -> the logger info-drop gate is inactive in prod so ALL info-level appEvents persist, incl benign well-known bot-probe rows that option-A intended to drop. Two parts: (1) verify whether LOG_LEVEL>=3 in Vercel env is intentional or leftover debug (broad appEvents-volume impact, not just well-known); (2) if benign well-known should truly vanish, switch to explicit skip-persist for isBenignWellKnown rather than relying on the LOG_LEVEL<3 gate. No page either way; harmless info/navigation rows. Not urgent. · pluto