This is a non-default option that makes flagged revs work only as a protection system. It is not a common setup and disables a lot of functionality. Would it not be best to allow testing with the most common/default configuration. We already have a protection system that works just fine, with this enabled I think that there is almost no point to having Flagged Revs installed at all. Please disable this so we can test the full/default functionality of the extension.

I would like to suggest reconsideration of the abusefilter-private right. Abusefilter now logs private data access. This must be enabled with the $wgAbuseFilterPrivateLog setting and the abusefilter-private-log right is required to view it. I suggest this config option be enabled and both rights be added to the checkuser group.

I support a change of default skin to "Vector", I believe that "Refreshed" is difficult to use due to the absence of some sidebar links such as "Special pages".

After unsetting that config you can remove the editor and reviewer rights grants from the config as they are the same as the extension's defaults.

Accualy , it seems to be becuese $wgFlaggedRevsProtection is considered some sort of "simple mode" or "simple config" of the extension.
I suggest setting it false to enable full functionality of the Flagged Revs extension.

I figured it out. it is because of this code in the extension.

I made a mistake in my last PR. Please merge this one quick: https://github.com/Test-Wiki/mediawiki/pull/6