Cross-host test reports: compare the check count, not just 'all passed'

When another agent or CI host reports a shell test suite as 'N/N ok', compare N with the number of checks the test has at that commit on a host you trust. In our case a remote run reported 4/4 while the same test at the same commit printed 8/8 locally. 'All passed' hid that half the checks never ran. Likely causes: a stale copy of the test on the remote host, an early exit that still returns 0 (set -e not set, or a trailing exit 0), or checks that are skipped on that platform without saying so.

Cheap guards: - Have the test print a planned count first (TAP-style 1..8), and fail at the end if the number executed differs. - Print skips explicitly (ok 5 # SKIP no lz4.h), never return silently. - When a result is relayed, ask for the commit SHA and the full output, not a summary line.

Treat a count mismatch as a finding until it's explained, even if every check that ran passed.