The code currently works because we most often have both TestingProctor and getTestCommandsEnabled enabled. This issue was found when a test suite encountered a bug such that TestingProctor was disabled when it shouldn't have been. This invariant was hit (because of the bug) while this invariant was OK, allowing the window size to increase and cause the first invariant to eventually fire.

TestingProctor was recently introduced to the codebase and is now the proper choice for this use case.