The live view drew a frame per instruction, so watching clb_digits walk its 13 cell
scratch block meant dozens of frames of "pointer moved one cell". Now a run of
STP/BTP closes into a single frame whose status line says where the pointer went
(`ptr +5 cell 91`), and `--skip-moves` does not render moves at all, only counts
them until the next data instruction.
Both are view-only: src/rot8.c, rot8_mem.c, the instruction behaviour, the step
count and the tape reader are untouched (git diff shows rot8_viz.c, rot8_viz.h --
one bool -- and vm_test.c's option parsing). The live path cannot be compared byte
for byte with a non-live run, because live mode sets quiet + replay_output=false on
purpose (the frames are the output); the checks are therefore:
* non-live stdout before and after: `--input R8F tapes/serial_echo.rot8` -> R8F,
the calculator tape at cell 11 with `12 34 + .` -> "> 0046" -- both unchanged;
* executed instructions: 280616 for that calculator run, identical to before;
* frames at -e 1 on that tape: 280616 -> 104423 (-63%) draws, and 65234 (-77%)
with --skip-moves; 215382 of the 280616 instructions are moves, in 39189 runs;
* at the default auto rate (every=1592 here) the draw count is 627 either way: a
frame that falls due inside a run is deferred to the run's end, never dropped.
ROT8_VIZ_FRAMES=1 makes a run print `draws/steps/moves/runs` to stderr, which is how
the numbers above were taken; it is documented in the README next to --live.