Context
We'd like to be able to invoke AbuseFilter actions if an edit doesn't pass the "likely to be reverted" revertrisk threshold.
Proposal
Introduce an AbuseFilter condition that utilizes the pre-save revertrisk API (T356102: Allow calling revertrisk language agnostic and revert risk multilingual APIs in a pre-save context) for the language agnostic model.
We'd have to exclude page creation scenarios, because the revert risk model doesn't handle those.
Consequences
- Abuse mitigation tooling can invoke actions before an edit is saved based on a revert risk score