When a game's launcher card has defined only a loop count, but doesn't define specific frames to loop through, the Launcher doesn't consistently end on a specific frame of the card-highlighted sequence.
I experienced it here with Dash Arena's card — this game's animation.txt governing the card-highlighted images contains only loopCount = 1 with no further instructions.
When the card is first highlighted after being brought into frame, the Launcher will loop through the frames in sequence, and then loop back around to the first image in the sequence before stopping.
On subsequent replays (if the card is un-hovered but kept in frame so it doesn't unload; and then re-hovered again), it will cycle through the frames like usual, and then stop on the final one instead of looping back like (I assume) it should.
This doesn't happen if the game defines frames in its animation.txt field alongside a loopCount; in that event, the Launcher will always stop on the final frame defined in frames.