When persistent vandalism occurs typically a page will result in being protected... without detecting this it will also trend.
@Pchelolo might know a little better, but there is https://github.com/wikimedia/mediawiki-event-schemas/blob/master/jsonschema/mediawiki/page/properties-change/1.yaml, which might have this. I'm not sure.
Looking to the code, it seems like the page protection is not a page_property, so it's not accessible via the properties-change event and changing it doesn't emit a new event.
+1 on emitting an event from the ArticleProtectComplete hook, but I would argue that conceptually that should not be a new event. My instinct was the same as @Ottomata's in that I thought protection changes should be a properties-change event; protection in my mind is a page's property.
@mobrovac Hm... The page-properties are a well defined concept in MediaWiki and it's pretty separate from the page-restrictions, they're even stored in a separate table. The properties are a map with string key and unspecified value, while restrictions are an array.. Also, restrictions can have additional properties like expiry and cascading, so if we add a separate schema for the we'd probably be able to make a better more restrictive schema.. But I'm ok with trying to put it to the properties schema as well, just don't quite see the benefit.
Interestingly, I noticed Steve Bannon trended yesterday but got some vandalism and ended up being protected, so excluding protected pages is probably not the best thing to do.. but maybe a protection could negatively impact the score just like reverts do.