phase-13 log: night-7 session research state (collision economy, myomer system complete, coolant leaks, the seek 4.0-vs-4.10 drift) + open-questions entry for the seek player version-probe

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019Zh7PTkFy4KwTzVighLR9J

context/open-questions.md

@@ -161,6 +161,17 @@ register.  ⚠ The audit also flags the damage-economy item as SELF-CONTRADICTOR
 (task #8 "landed" vs the kShotDamage=12 bring-up residue) — audit before reworking.
 
 ## Deferred subsystems / feeds (authentic path scoped, marked in code)
+- **Myomer seek "SUPERCHARGE" — 4.0-manual vs 4.10-binary, AWAITING THE PLAYER VERSION-PROBE
+  (2026-07-31).**  The 1995 manual (p20/p22 + stat sheets) says seek changes TOP SPEED (gear 4 =
+  "Supercharge", expert-only; Loki/Thor print Normal 143 / Super Charged 182 / Gimped 40 kph).
+  The 4.10 binary provably has NO runtime myomer→speed coupling (full data-flow closure [T1]:
+  demand fn @004afd10 all branches, all speedDemand writers, AvailableOutput's 2 callers, the
+  virtual slot-0x3C sweep, the single SpeedEffect attr ref, the 0x7A0 writer set — see
+  phases/phase-13).  Printed ratio 1.27 vs 4.10's vestigial gear ratio 1.43 → documented
+  4.0→4.10 drift.  The operator is asking SAURON/Oracle whether THEIR pod-era mechs sped up at
+  seek 4.  If yes and wanted: resurrecting supercharge is an OPT-IN deviation — the plumbing
+  (gear ratio, 0x7A0 cap, ratio² heat, heatFactor overheat-to-zero) all exists; it needs one
+  authorized multiplication in the demand path.  [[subsystems]] [[pod-hardware]]
 - **Environment gravity unwired — the myomer CLIMB-heat term is inert (found 2026-07-31, #85).**
   `Mover::localEnvironment` (MOVER.h:271) is declared and never populated anywhere in the port;
   `GetEnvironment()->gravityConstant` is the named analog of the 1995 Mover's gravity POINTER at