Changes

Terminal Guidance correctness bug

This seems a bit useless/dangerous to me.

We explicitly catch all the cases when we should exit terminal
guidance above here.  While this will potentially blow up if we
ever call it and grab a zero-dV stage or small ullage stage that
is below minDV and isn't part of the solution.

It seems like we should just loop and wait for the stage and/or
solution to update to something that agrees, or else loop until
one of the explicit conditions at the top handles exiting
properly.

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
 (commit: 4cde5c3)