feat: log the game's high-score report as a gameplay event

When the game builds its high-score table report for Stern's agent
(/api/v1/game/high_score_events - the endpoint the Insider gate already sits
on), the logger writes an HSTD line with all four players' scores. This is
the report the game sends when a game has changed the table, so the line
marks a high-score event with no new per-game RE. The entries themselves
(initials, position) live deeper in the report body and stay uncaptured for
now - that needs locating the report builder or the in-memory table.

Tests: the endpoint trigger and the HSTD line lift into the host harness
(the endpoint pointer is a 32-bit register, so the harness maps its string
below 4 GiB and the tests run on the Linux leg like the port-gate ones).

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

shipper/init.d/log_shipper

@@ -1,10 +1,12 @@
 #!/bin/sh
 # log_shipper - tail /dump/*.log and push them to Loki (see shipper/README.md).
 # Config comes from the environment; defaults in the binary match the machine.
+# The shipper's own complaints land in /dump/logshipper.log (a few lines a boot).
 
 case "$1" in
   start)
-    start-stop-daemon -S -b -m -p /run/logshipper.pid -x /usr/local/bin/logshipper
+    start-stop-daemon -S -b -m -p /run/logshipper.pid -x /bin/sh \
+        -- -c 'exec /usr/local/bin/logshipper >>/dump/logshipper.log 2>&1'
     ;;
   stop)
     start-stop-daemon -K -p /run/logshipper.pid