test: count what was skipped, and say how to stop skipping it

The suite reported 73 passed, 0 failed on a machine where it had been
reporting 87.  Nothing had regressed: the VM had been booted without a
second card, so the fourteen card-mode checks skipped.  A skip printed
one line among ninety and the total moved, and a total that moves is
not a signal anybody reads -- 73 passed looks exactly as good as 87
unless you happen to know which to expect.

So skips are counted with the rest:

	87 passed, 0 failed, 0 skipped

and the one that matters says what to do about it rather than only what
is missing: boot with run.sh -gw and the spare card is there.  The
header says the same, since that is where someone looks first.

Also finishes the proof the last commit could not.  /sys/log/fw now has
a line for every port the suite can pick, so the collision that made
the old check fail by chance is certain: 3600 poison lines, and the
delta version passes 87 while the total version fails both logging
checks with 4 and 3 where 1 is right.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions