Back to normal.. phew! :)

@Jdlrobson The commit doesn't appear to have had the intended effect, re-introducing T279008:

The added rule that you meant as override is shipped before the broken rule that it re-enabled. (about 500 lines between the two in the SkinModule response)

Perhaps it would be easier to add the one line of code from this new core rule that we actually need instead of shipping multiple copies of the same thing that are meant to cancel out (but didn't). Or since none of all these were meant to have any noticable affect on the user, to restore to the last-working state until there is time to research it better whilst master and production are not used as test bed. This is the third week in a row that the same refactor once again didn't work out as expected from causes that were rather predictable.

Thanks for flagging but the issue here with the elt element is fixed.

I'd rather prioritize T279388 and get this done properly so I've moved that into the sprint board. As these last few weeks have proved it's not worth rushing a temporary fix, particularly during a time when this team is under pressure from multiple angles for a bug that this team does not recognize as unbreak now.

Note: in case it wasn't clear the ship sailed a long time ago (before the last version) for us to be able to restore the last working state due to the extension/skin/core relationship and at this point identifying and reverting squashes of all the patches involved here feels like the same amount, if not more work than actually taking the time to fix this properly. Currently, T270027 is higher priority than this hence the delay in my ability to focus on this.