EDIT: Sorry about the wall of text mate haha, hopefully it isnt too annoying to read 
Mmm I definitely appreciate that there have been countless mis-cited bugs, and inaccurate reports, you are undeniably right about that. But that seems to be an inevitability when it comes to any process similar to this e.g the reproduction of a game, and as a result it definitely falls on the bug ticket issuers as a responsibility to explain their reports as thoroughly as possible and with as much credible supporting information as possible.
To that end I have tried to, provide as much information as possible surrounding these ideas, so this definitely isnt just a random “This is bugged fix it!!11” post haha.
That being said I think moving goal posts is actually an awesome thing rather then a bad thing haha, I mean think about it, what that actually implies is that we have for the most part confirmed undeniably that a large part if not the majority of the game is as close to the original as possible, the more the goal posts move, the better it actually is, until they hit the finish line and we can finally say, this is undeniably and indisputably as close to vanilla as it could be… So lets keep those goal posts moving!
Finally the question of am I certain, lets look at what is certain, Seal Twisting was established and discovered in The Burning Crusade for the most part, that is why the majority of evidence surrounding it is TBC era, so that is the reason for TBC evidence provision, we know Seal of Command is not functioning the same way in Classic as it did in Vanilla, you could cast Judgement instantly or swap seals instantly as the White Swing hit a target in the original version and still get a command proc… you cant in classic, if you swap seals instantly on white swing in classic and resultantly before the calculation is parsed during the next spell batch you will not cast command… that is an indisputable change and correlation between the two versions of the game, and is documented in videos.
Looking further we also know that seal twisting affected both the inital hit and the following command proc in the original game, in classic you can only seal twist the command proc following a white swing once it has procced e.g proccing Seal of Justice off of Seal of Command… a result of the new seal cast not being in the same spell batch as the initiating white swing, seals in classic are applied to white swings in the same batch, that we know is definitely true… and is why command can be applied retroactively by paladins after a swing has already landed… this explains why we dont see double procs while twisting e.g 1 off the initial white and 1 off the procced command hit, like we did in the original game.
Finally Seal of Righteousness procs off of every melee hit no matter what for a paladin, even if the taget is immune it will say the target was immune. Based on this knowledge of the interaction it is pretty clear; we know the spell is not working correctly and we know how the interaction should work, if the system functioned correctly, you should be able to twist Seal of Righteousness off of it, and even if Seal of Command didnt return a Seal of Righteousness hit (which it should since it is for all intents and purposes a melee swing), the initial White Hit definitely should since every white hit returns SoR, resulting in a sequence of:
White Hit + SoR Hit + SoC Hit
However because the PPM calculation of SoC has been pushed back to the spell batch, it is impossible to return this sequence because the new application of SoR will be on a different Spell Batch to the white hit…
So once again, we know seal swapping/judgement casting could be perfomed as soon as the white hit occured in the original game, in classic it cant, we also know that batching isnt an authentic recreation of the system, it was an emulation of it… they literally announced it themselves in the initial post:
So if you are asking if I am sure; I am… however the reality is it isnt really a matter of whether im sure or not, the evidence undeniably proves where the issue lies, we know Seal of Command isnt performing in the same way as it originally did, and it is the cause of the issue.
