slow-query notice prints to stdout and writes NO ledger row — classify.ts:133's slowQueryPageMs gate has had nothing to act on

Observed by coder-venus-cc during the VENUS-333 send, reported untriaged rather than swallowed. stdout carried '[pg slow 902ms] SELECT "campo", "id" FROM "lookupOptions" WHERE "grupo" = ...'. CHECKED BEFORE REPORTING: appEvents holds ZERO action='slow_query' rows in the last 7 days and ZERO EVER matching that statement -- so the notice printed to console and LEFT NO LEDGER ROW AT ALL. Two readings that cannot be separated without opening the slow-query writer: (a) the CLI/tsx path logs slow queries to stdout only, or (b) the write path is broken. CONSEQUENCE EITHER WAY, and it is the point: classify.ts:133's slowQueryPageMs gate -- enumerated as LIVE in the VENUS-327 5/9 count -- IS ON THE EVIDENCE UNEXERCISED, because nothing ever reaches it. A gate with no population is not a gate; it is a claim. Determine which reading holds, then either wire the write path or strike the gate from the enumeration with a stated reason. Do NOT close by picking the tidier reading.