Prop354: Improve conflux restriction; clarify issues
This MR changes the conflux restriction to only forbid both guards from being the same, UNLESS one of the guards is chosen as the Exit first.
This change should now mean that the rules will successfully terminate, even implemented async, as-is.
I also tried to explain this a bit more in the remaining issues section, as per @gabi-250's question on #307 (comment 3189466)