Another solution to this ticket might be to stop having the patrol API mark pages as reviewed in PageTriage. In other words, force new page reviewers to use the Page Curation toolbar. This would involve some complaints during the initial disabling, but would clean up the logs in the long run, reduce code, and get rid of the unintuitiveness of this patrolled vs reviewed thing.

Perhaps adding some code to hide the [Mark this page as patrolled] link from everyone at all times is the way to go here. Downside is if someone has a workflow of clicking this link in non-mainspace, this would disrupt their workflow.

• post at WT:NPPR and WP:VPT, ask if this would break anyone's workflows
• see if folks do something weird with patrolled edits in other namespaces, such as checking every uploaded file in the file namespace and marking it as patrolled
• wikimedia-site-request to turn off patrolled edits (hopefully getting rid of the patrol API, the [mark this page as patrolled] link, and the red exclamation mark in recent changes, but without messing with the patrol userright) (test and see if this is possible)
  • $wgUseRCPatrol = false; - exclamation marks in recent changes
  • $wgUseNPPatrol = false;
  • $wgUseFilePatrol = false;
• remove patrol API calls from PageTriage

Might want to start a discussion at WT:NPP to gauge how many people still use the patrol button instead of the curation toolbar. Also, can we disable the button in mainspace only? That would be the best of both worlds in terms of unlinking it from PageTriage while causing as little change as possible.