Friction-log-driven UI fix campaign (fleet)

Elazar directive 2026-07-18: all apps have FRICTION-tier telemetry (appEvents category='toast', mechanism validation-fail/native-validation/inline-hint + user-facing warnings/feedback). Mine it and FIX the UI causing the friction - don't just suppress logging. Per-app: (1) query friction-tier appEvents over a recent window (2-4wk), (2) rank friction sources by frequency, (3) root-cause + fix the top offenders (clearer labels/defaults/pre-fill/inline hints, remove needless required-field friction), (4) report top sources + fixes (SHAs) + residual. Class-S mostly; anything touching auth/schema/email = Class-A gate. Reference model: prior Mars campaign cut logged toasts from hundreds/week to <12. Scope: mars+pluto+venus (live apps w/ friction data); enamel excluded until it has a friction surface.