huhh, yeah, i see what you mean. it seems to be timing-based, where if you move during the scene transition it uses the prior cell's directional state instead of the current cell's. presumably while twine is doing the transition both passages are loaded and so my code grabs the wrong copy, or something.
well thanks for the bug report; i'll see if i can fix this one!