Bug fix affecting solve with given moves

Actually two bugs, the first one with no known effect:  mv.sequence should of course
be 0 to begin with.

The move object was not being initialized prior to insertion of a given move.