Friction-telemetry unification: one feedback chokepoint, canonical category=toast+mechanism, server-action transport, complete logs friction view

Elazar 1a2a3a4a (via audit-mars-ca 2026-07-12): full root-cause friction-telemetry unification, no deferrals/bandaids. (1) ONE shared typed client feedback primitive every friction surface routes through: error/warning toasts, inline errors, native HTML5 validation, dialog error/guide/confirm/dismiss/abandon phases, banners, nudges (rectificar, read-only guidance). Success confirmations stay excluded as noise; info guidance/nudges included when they represent friction/required attention. (2) Canonical category=toast + detail.mechanism enum extended: toast|native-validation|inline-hint|dialog|banner|nudge. (3) Replace /api/log-toast (and friction portion of /api/log-ux-event) with server-action transport (adblock-immune per fleet std). (4) Make /administrar/logs?category=toast the COMPLETE canonical friction view incl migrating/normalizing existing category=ux friction rows (db-mars owns the appEvents backfill). (5) Adopt useActionForm across all forms OR fold into new primitive - kill its dead-code state. (6) Fix double-log: checkRequired currently emits error-shown+validation-blocked=2 rows/block -> collapse to 1. (7) Repo-wide census + enforceable lint/test so new direct setError/setDialogError/native feedback cannot bypass the chokepoint. (8) Verify prod with representative events per mechanism + query counts/view. Coherent split commits, preserve behavior. Pre-impl audit design-ping + db-mars migration coordination required (data migration).