route.ts: /api/log-error outer catch swallows its own failures, no appEvents row

route.ts outer catch (~470-487) returns {ok:false} on any failure and writes no appEvents row — no logEvent call, no alert. The app's own client-error reporter silently discards the client's error report when the endpoint itself fails. Violates evolutiva-commons §No Silent Failures. Fix: wrap outer catch to still emit an appEvents error-tier row (best-effort, must not throw) before returning ok:false.