Coercion variables appearing where they shouldn't
During review of !2268 (closed), we've discovered a few places where a coercion variable can appear where it shouldn't. Those are calls to "OrCoVar" functions in:
that happen when running tests T13990 T14285 T15648.
The goal is to fix this, or come up with a convincing reason that a coercion makes sense there.