BT410 5.3.56: the intermittent pod crash is the skeleton walk's -- attributed by same-binary A/B

Added BT_NO_SKL, which skips the skeleton build so ONE executable can be run
with and without it.  That is the only clean way to test an intermittent
fault, and it settles attribution:

  walk enabled   ~50% of runs die (page fault at 66D9) at DIFFERENT points
  walk disabled  0 crashes in 2 runs
  shipped exe    0 crashes in 2 runs, same rig and conf

So it is our new code, not the rig, and the varying fault point points at
memory corruption surfacing later rather than a bad instruction in the walk.

Hypotheses killed by reading the private library headers: the matrix array is
the right size (dpl_MATRIX is float32[4][4]); and neither s_dplobject nor the
common dpl_node header retains an object name, weakening the dangling-string
theory (a private name cache inside the library is still possible and is the
best surviving suspect).

Also checked something that would have been much worse than a crash:
~NotationFile REWRITES its file when dirty, and these are the game's shipped
.SKL data files.  MAD.SKL is untouched, and ReadSKLFile now carries the
engine's own Verify(!IsDirty()) guard.

Next tests are listed cheapest-first in the roadmap: keep the NotationFile
alive, copy the Object= names, count board allocations, and re-check whether
MakeEntityRenderables runs twice per mech.

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

emulator/render-bridge/pod_render_noskl.conf

@@ -0,0 +1,70 @@
+[sdl]
+output=opengl
+# higher,higher not highest: HIGH_PRIORITY_CLASS starved the host desktop;
+# with the retry patches a rare dropout self-recovers (see gauge_rio.conf).
+priority=higher,higher
+[dosbox]
+memsize=32
+machine=svga_s3
+[cpu]
+core=dynamic
+cputype=pentium
+cycles=max
+[sblaster]
+sbtype=sb16
+sbbase=220
+irq=5
+dma=1
+hdma=5
+[mixer]
+# match the EMU8000s' native rate (no resample) and buffer ~60ms so brief
+# emulation-thread stalls (RIO retry recovery) don't audibly chop
+rate=44100
+blocksize=1024
+prebuffer=60
+[serial]
+# RIO on COM1 with the low-latency options (rxpollus/rxburst) so the board's
+# few-ms ACK deadline is met; plasma display on COM2 (real pod has both).
+# VWE fork namedpipe backend (com0com/realport retired -- COM1/COM2 gone):
+# DOSBox = pipe client (retry), vRIO/vPLASMA apps = servers; an unconnected
+# pipe behaves as an unplugged cable so the mission still runs. serialnamedpipe.h
+serial1=namedpipe pipe:vrio rxpollus:100 rxburst:16
+serial2=namedpipe pipe:vplasma
+
+# live UNBUFFERED game output: DOS char devices are not buffered, so
+
+# redirecting stdout to COM3 lands every line immediately.  A normal
+
+# '> file' redirect stays 0 bytes until the process exits, which hides
+
+# all progress on a run that does NOT crash.
+
+serial3=file file:C:\VWE\TeslaRel410\emulator\render-bridge\podlog.txt
+[autoexec]
+mount c "C:\VWE\TeslaRel410\ALPHA_1"
+c:
+cd \REL410\BT
+set VIDEOFORMAT=svga
+rem production pod card init (PARAMETR.BAT:181-186): DIAGNOSE + AWEUTIL per
+rem card -- AWEUTIL /S does the EMU8000 bring-up and DRAM detect the HMI SOS
+rem driver relies on; skipping it left the cards uninitialized (silent).
+rem aweutil /s SKIPPED for now: it verifies the AWE32 GM ROM, which the
+rem emulated cards lack (hangs in a retry loop) -- restore once the ROM is
+rem dumped from a real card. diagnose /s kept (passes, sets mixer config).
+set BLASTER=A220 I5 D1 H5 P330 T6
+c:\sb16\diagnose /s
+set BLASTER=A240 I7 D3 H6 P300 T6
+c:\sb16\diagnose /s
+set BLASTER=A220 I5 D1 H5 P330 T6
+set TEMP=c:\
+rem arena1 city mission (TESTARN.EGG: map=arena1, time=day) with the RIO
+rem attached; stdout redirected so mission-load progress survives kills.
+set BT_NO_SKL=1
+set BT_FORCE_THROTTLE=0.6
+set BT_FORCE_TURN=0.25
+set HEAPSIZE=15000000
+set L4GAUGE=640x480x16
+call setenv.bat r s n p
+32rtm.exe -x
+BTL4REC.EXE -egg testarn.egg > COM3
+

emulator/render-bridge/podlog.txt

@@ -8,7 +8,6 @@ ColorMapperArmor warning: damage zone dz_lmissle not found
 ColorMapperArmor warning: damage zone dz_rmissle not found
 ColorMapperArmor warning: damage zone dz_ftorso not found
 ColorMapperArmor warning: damage zone dz_btorso not found
-L4VIDEO.cpp wrong video resource type for object mad.skl
 BTL4Application::RunMissionMessageHandler
 Turning Plasma Score Display On
 BTL4Application::RunMissionMessageHandler

emulator/render-bridge/podlog_shipped.txt

@@ -1,7 +1,7 @@
 BattleTech v4.10
 BTL4Application::BTL4Application
 GaugeInterpreter: undefined label 'Initialization'
-MakeVehicleSystems hud=0x011503f0
+MakeVehicleSystems hud=0x01154164
 Warning: damage zone 'dz_missle' not found!
 Warning: damage zone 'dz_missle' not found!
 Warning: damage zone 'dz_lmissle' not found!
@@ -9,7 +9,9 @@ Warning: damage zone 'dz_rmissle' not found!
 Warning: damage zone 'dz_ftorso' not found!
 Warning: damage zone 'dz_btorso' not found!
 LBE4ControlsManager::Execute, lost RIO analog request
-iThinkIRQIsOn =1, actual state =1, characters sent =713
+iThinkIRQIsOn =1, actual state =1, characters sent =62
+LBE4ControlsManager::Execute, lost RIO analog request
+iThinkIRQIsOn =1, actual state =1, characters sent =687
 BTL4Application::RunMissionMessageHandler
 Turning Plasma Score Display On
 BTL4Application::RunMissionMessageHandler