feat: arm the switch-edge logger — add switch sites, values and buttons to the KK LE port

The v3 runtime's edge logger could never arm: the port had no switch_edge /
switch_drain sites, no switch_records/switch_count data and no switch_*
record-layout values, and switches_arm() skips a port without switch lines.

Located in the King Kong LE 0.97 ELF with the decryptor's
portswitch.switch_source() (generation-B framework): switch_edge 0x0055fa04,
switch_drain 0x005606e4, switch_records 0x008ecc78, switch_count 0x0093437c;
record layout 384/32/24/8/26/28 as on the other generation-B builds. Added
LOCKDOWN/START/flipper button switch lines on bits the game's shot dispatch
never sends, so the logger arms and the buttons become named shots.

Deployed to the machine and verified in play: the boot log arms the drain
(switch_edge 0x0055fa04, drain 0x005606e4..0x00560864) and /dump/switch.log
logged ~6000 in-game edges, both edges of all four flipper buttons, named.

Also fixes the runtime's mangled GAMELOG comment (broke the build) and the
switch_names.inc entry count in the README.

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

README.md

@@ -18,11 +18,14 @@ why, and the game runs stock.
 | Shots (`SHOT`): every named shot dispatched while a ball is up | **deployed on the machine, verified in play** |
 | Stock modes (`gamelog: MODE START/END`): the game's own 22 modes with score delta | **deployed on the machine, verified in play** (`mode_score` is approximate) |
 | Award screens (`AWARD id=…`): every award the game shows, extra-ball tracking | **deployed on the machine, verified in play** — except the extra-ball award id is not yet confirmed (below) |
-| Switch/button log (`/dump/switch.log`, `SW` lines with generated names) | **implemented in this tree, NOT yet deployed or verified** — the deployed `mode.so` (built 2026-10-12 10:46) predates it |
+| Switch/button log (`/dump/switch.log`, `SW` lines with generated names) | **deployed on the machine, verified in play** (flippers on both edges; sites located with `portswitch.switch_source` and added to the port) |
 
-The machine currently runs the v2 build (events, shots, modes, awards). The
-switch logger (v3) is in this tree and needs a rebuild + redeploy before it can
-be relied on.
+The machine currently runs the v3 build (events, shots, modes, awards, switch
+log). The v3 work needed more than a rebuild: the port had no `switch_edge` /
+`switch_drain` sites or `switch_*` values, so the runtime's edge logger could
+never arm. They were located in the King Kong LE 0.97 ELF with the decryptor's
+`pinball_decryptor.plugins.stern.portswitch.switch_source()` (generation-B
+framework) and added to `ports/king_kong_le-0.97.port`.
 
 ## Files
 
@@ -30,7 +33,7 @@ be relied on.
 |---|---|
 | `gamelog.c` | the logger: a passive PAD mode. It never `pm_begin()s`, never blocks, allocates nothing — it only watches and writes `[GAMELOG]` lines |
 | `pad_mode_runtime.c` | the PAD Modes SDK runtime, **patched**: (a) a GAMELOG section — passive stock-mode and award watching, exporting `gl_award_seq()` / `gl_last_award_id()` to modes; (b) the per-edge switch logger to `/dump/switch.log`; (c) the Insider Connected gate made passive. Our exact changes vs upstream: `docs/runtime-patch.diff` |
-| `switch_names.inc` | King Kong LE 0.97 switch id → name table (103 entries), `#include`d by the runtime's switch logger. Generated from the game's own data (method: `swnames.py` in the decryptor repo); fix names here if any are wrong |
+| `switch_names.inc` | King Kong LE 0.97 switch id → name table (104 entries, ids 1–104), `#include`d by the runtime's switch logger. Generated from the game's own data (method: `swnames.py` in the decryptor repo); fix names here if any are wrong |
 | `pad_mode.h`, `pad_stock.h` | unmodified SDK headers (needed by the build) |
 | `build_mode.sh` | unmodified SDK build script: compiles the runtime + your mode into one `-nostdlib` shared object and refuses banned libc calls |
 | `event_probe.c`, `event_read.py` | the event-bus measurement instrument and its log reader — how bus event ids are identified for another game (MODE_SDK.md, "Measuring events on another game") |
@@ -169,11 +172,6 @@ The ids you name that way become the `event` lines of a port (the six in
 
 ## Unfinished work / known issues
 
-- **The switch logger is not on the machine yet.** The deployed `mode.so` is the
-  2026-10-12 10:46 build (events/shots/modes/awards). The `/dump/switch.log`
-  feature (runtime patch + `switch_names.inc`) was written later the same day:
-  it needs a rebuild, a redeploy, and verification that the log appears and the
-  names are right.
 - **The extra-ball award id is unconfirmed.** Default 13 is a static guess from
   the game's object-name tables; every award id is logged, so earn an extra
   ball, read the `AWARD` line, and pin it down (or override it in the port).