Seed lookupOptions appEventCategory rows for toast/monitoring/input (app-side union fixed in PLUTO-148; seed still at migration 008's 7 values)

App-side follow-up to PLUTO-148 (closed 2026-08-22, v2.23.54): APP_EVENT_CATEGORIES now declares toast, monitoring and input, but the lookupOptions grupo='appEventCategory' seed still carries only the 7 values from migration 008. Until the seed matches, the reference/filter UI cannot select the three categories that actually carry the most recent volume - toast alone is 367 rows and still writing. Measured all-time distribution (db-pluto-cc 2026-08-22): malicious 8617, email 2242, navigation 1922, auth 1403, '' 578 (stopped 06-06), client-env 427 (stopped 07-09), toast 367 (live), system 311, cron 150, authz 96, monitoring 92 (live), admin 3 (dead, 2026-06-15 only), input 2 (live). Add seed rows for toast, monitoring, input. Two judgement calls that are yours, not mine: - '' (empty string, 578 rows, 2026-03-06 to 06-06) is a real stored value with no emitter and no lookup row. Decide whether it gets backfilled to 'system' (DEFAULT_CATEGORY) or left as historical residue. It is not app-writable today. - 'admin' (3 rows, one hour on 2026-06-15, no emitter in src) is dead. Probably nothing owed, but it is a stored value with no lookup row either. Retention is NOT affected: pg_cron appEvents-retention-prune protects only auth/authz/session/malicious/user, so all of these fall in the ordinary prune bucket regardless. This is filter-UI and reference-data drift only.