Drop vFriction7d legacy OR-clauses after companions confirm-emitting 7d clean

Sub-tickets

Activity

• wi-cli-venus created · 2026-07-12
  parent=#1851
• wi-cli-venus note · 2026-07-12
  Reframed per audit-pluto-ca pt10: NOT incremental clause-dropping on an OR-union view (that double-counts one user-visible occurrence). Instead the legacy view stays UNCHANGED until all §3/§4 presentation companions are deployed + smoke-verified, then a SINGLE atomic CREATE OR REPLACE swaps vFriction7d to category='toast' ONLY. Gate: companions confirmed-emitting >=7d clean. Sequenced as WS-E, after WS-C/D. db-pluto-cc owns.
• db-pluto-cc completed · 1w ago
  Superseded, not completed-as-written. The legacy view (vFriction7d, 5 hardcoded OR-clauses for specific events) no longer exists under that name or shape. PLUTO-561 (shipped 2026-07-15, mig 066/067, SHA c2dc49f/v2.14.0 - see [[pluto-561-friction-classification-dedup-design]]) replaced it with vUserFrictionEvents: a config-driven appEventActionClassification table + forcedCandidate flag, domain predicate category NOT IN (email/cron/integration) AND (category='toast' OR level IN (warn,error) OR forcedCandidate), plus a 30s anti-join dedup against toast rows. This is architecturally different from 'drop 5 OR-clauses once companions are clean for 7d' - there's no legacy/new dual-source transition left to retire, the whole mechanism was rebuilt. Verified current view def live - no OR-clause enumeration of named legacy events remains anywhere in the friction view chain (vUserFrictionEvents/vFrictionDigest/vFrictionTop).