Torso: the TWIST goes LIVE -- electrical watchdog chain, centered crosshair, coherent controls (task #57/#58)

The MadCat torso twists, the view turns with it, and targeting follows.
Three reconstruction fronts closed:

THE ELECTRICAL WATCHDOG CHAIN (why the torso never powered up):
- PowerWatcher::UpdateWatch reconstructed (@004b181c, the REAL registered
  Performance -- PTR @0050f5fc; Ghidra missed the fn start): the watchdog
  MIRRORS the watched subsystem's electrical level (+0x278), brownout
  downgrade when gen output <= minVoltage% x rated.  @004b1804 relabeled
  ResetToInitialState (slot 10) -- the old "Simulation" tag was wrong.
- The factory watcher-CONNECT pass reconstructed (vtable slot +0x38,
  @004aee2c/@004b1a40 byte-identical, recovered from raw exe bytes):
  watchedLink.Add(roster[watchedSubsystem]) on the master node.  Was the
  SubProxy::Start() no-op -- every watchdog sat at 0 forever.
- MinVoltageScale = 0.01 (a 10-byte x87 literal @0x4b1924; was 1.0f =
  permanent brownout) and PowerWatcher's Derivation chains its REAL base
  HeatWatcher (the HeatableSubsystem stand-in broke IsDerivedFrom for the
  whole Torso/Searchlight/ThermalSight family).
- KB correction swept: derivation tag 0x50e604 = HEATWATCHER (not
  "HeatSink"); the btl4gaug heat-widget gate now tests it via the
  BTIsHeatWatcher bridge.

THE CROSSHAIR (task #58 forensics, 6-agent workflow + live probes):
- The VIEW is TORSO-MOUNTED: jointtorso -> jointeye -> siteeyepoint in
  every twist-capable .SKL; the camera + canopy ride the same hinge
  subtree through HingeRenderable's live matrix-stack compose -- ALREADY
  WORKING in the port.  The crosshair stays screen-centered (center IS
  the boresight); the twist reads on the tape carets/compass/radar.
- The real bug was the port's gBTAimX = tan(twist) slew (the falsified
  "body-mounted view" model): the camera already carried the twist, so
  the crosshair counter-slid to hull-forward and the fire ray with it.
  Deleted; the pick ray inherits the twist from the yawing eye basis.
- Two instrumentation traps documented (chase-eye-as-default-camera,
  BT_FORCE_TORSO clobbering real joints -> the hook now only fills
  unresolved ones); an over-correcting explicit eye compose was added on
  those false readings and retired the same day.

CONTROLS + REPLICATION:
- Q/E spring-center on release (the axis is a twist-RATE demand; the old
  hold-deflection model drifted forever); X also zeroes the axis and
  pulses the authentic torso Recenter (@004b6918).  M cycles control
  mode via the real CycleControlMode body.
- Torso update-record DIRECTION fixed: engine truth is Write=serialize /
  Read=apply; @004b6a78 is the READ (was mislabeled Write) and the
  missing WRITE @004b6a1c recovered from raw disasm (recordLength 0x1C,
  twist/vel/rate at +0x10/14/18) -- kills the replicant's 0xCDCDCDCD
  -140-degree ghost twist.
- Marching-ghost desync: 4 Standing-case guards zero stale reverse
  cycleSpeed (negative cadence passed the <= ZeroSpeed stop gate).
- Kill credit rerouted to the OBSERVED killer (lastInflictingID ->
  killer's player link) -- kills count, target K/D populates.

KB: subsystems.md (watcher chain), multiplayer.md (record direction),
combat-damage.md + gauges-hud.md + cockpit-view.md (torso-mounted view
re-correction), decomp-reference.md (new addresses + tag fix),
open-questions.md (dead capability-roster loops 2-4, snapshot CD read).

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

context/combat-damage.md

@@ -32,29 +32,45 @@ player input). [T1]
 `mech+0x38c` = targeted sub-zone (−1=whole). Weapons cache hasTarget/targetPoint/muzzlePoint,
 refreshed each frame. [T1]
 
-**The AUTHENTIC acquisition model (recovered 2026-07-08; corrected 2026-07-08, task #39):** THERE
-IS NO FREE-AIM MOUSE CURSOR. The pod had a stick whose yaw drove the **torso twist**
-(`MechControlsMapper` writes `HUD::SetFreeAimSlew(stick_x)` → cockpit+0x28C, gated on the torso's
-horizontal-twist being enabled — `mechmppr.cpp:735/762`, hud.hpp:167 [T1]); the crosshair marks
-where the **torso guns boresight** relative to the body-mounted view. You aim by **steering the
-mech / twisting the torso**, not by moving a cursor. The engine `Reticle` struct
-(`engine/MUNGA/RETICLE.h`) carries `reticlePosition`, `pickPointingOn`, `rayIntersection`,
-`targetEntity`, `targetDamageZone` — a general struct shared with Red Planet — but in BT
-`reticlePosition`/HotBoxVector (@mech-HUD+0x1FC) is **COMPUTED by HudSimulation** from the mech
-pose quaternion (`FUN_0040954c` quat→euler of mech+0x10C) + the target geometry, and **zeroed to
-centre when there is no target** (part_013.c:5680, `FUN_00408440(...,&DAT_004e0f74)` [T1]) — it is
-NOT a free-floating cursor. The pick then hits whatever the guns point at; that entity + its
-DAMAGE ZONE become the target (`0x37c` rayIntersection, `0x388` targetEntity, `0x38c`
-targetDamageZone → aimed-zone damage). Fixed-torso mechs (the BLH: `TorsoHorizontalEnabled=0`)
-boresight dead-ahead — the crosshair sits centred and you point the whole mech. Once locked,
-`Emitter::FireWeapon` converges with NO aim/arc test (part_013.c:7758). `MechWeapon::
-UpdateTargetState` (`FUN_004b9bdc` [T1]): `targetWithinRange = dist < (1 − hostZoneDamage) ×
-weaponRange`. The 0x388 WRITER (the per-frame reticle→mech copy) is in an un-exported decomp gap.
-**Port status: RECONSTRUCTED + runtime-verified (tasks #36/#39, 2026-07-08) [T2].** The chain:
-the crosshair = **torso boresight** (`BTTwistToReticleX(torsoTwist)`, L4VIDEO — tan(twist)
-projected through the live per-axis projection; **0 = dead-centre on the fixed-torso BLH**;
-`BT_AIM="x y"` pins it for headless tests) → `BTGetAimRay` (the ACTIVE eye publishes pos+LookAtRH
-basis via `BTSetAimCamera`, the render loop publishes proj._11/_22 + backbuffer dims) →
+**The AUTHENTIC acquisition model (recovered 2026-07-08; task #39; RE-CORRECTED 2026-07-13, task
+#58 crosshair-twist forensics):** THERE IS NO FREE-AIM MOUSE CURSOR — and **the VIEW is
+TORSO-MOUNTED, not body-mounted**. The cockpit eye hangs off the torso yaw hinge in every
+twist-capable skeleton (`jointtorso` (hinge-Y) → `jointeye` → `siteeyepoint`; all 14 twist-enabled
+Torso records name `TorsoHorizontalJoint=jointtorso`; `Torso::UpdateJoints` writes currentTwist
+into that joint each frame; VIEW = inverse of the LIVE joint chain, `FUN_004c22c4`
+part_013.c:11742, no de-twist anywhere [T1]). So when the torso twists, **the CAMERA yaws with
+the guns and the crosshair stays SCREEN-CENTERED** — truthfully, because screen center always IS
+the boresight; the world rotates past it. The twist reads on INSTRUMENTS: the bottom 21-tick tape
+carets, the compass (= body yaw + twist, part_013.c:5674-5676), the radar wedge
+(part_013.c:11836-11859) [T1]. The old "crosshair = torso boresight offset in a body-mounted
+view" model was falsified — it was never discriminated before because every prior live test used
+the fixed-torso BLH, where both models center the crosshair.
+The engine `Reticle` struct (`engine/MUNGA/RETICLE.h`) carries `reticlePosition` (a variable
+screen position −1..+1 [T0]) — the reticle CAN move, but its writer is in an un-exported decomp
+gap (`s_TargetReticle` has exactly ONE xref binary-wide: the read-side lookup part_014.c:5132);
+the only coherent twist-era mover is the **fixed-torso free-aim channel**: `MechControlsMapper`
+writes `HUD::SetFreeAimSlew(stick_x)` → cockpit+0x28C **only when torso twist is disabled**
+(part_013.c:339-345/381-387 [T1]); HudSimulation integrates it (negated, part_013.c:5717) into
++0x294 clamped ±(+0x29C) → `mech+0x36c` every frame (:5735) — no exported consumer; the
+mech+0x36c → reticlePosition link is [T4]. NB: an earlier version of this section conflated
+`reticlePosition` with **HotBoxVector** (HUD+0x1FC — the TARGET designator HudSimulation zeroes
+with no target, part_013.c:5680); they are different things.
+The pick hits whatever the guns point at; that entity + its DAMAGE ZONE become the target
+(`0x37c` rayIntersection, `0x388` targetEntity, `0x38c` targetDamageZone → aimed-zone damage).
+Fixed-torso mechs (the BLH: `TorsoHorizontalEnabled=0` — no jointtorso in the skeleton at all)
+boresight dead-ahead. Once locked, `Emitter::FireWeapon` converges with NO aim/arc test
+(part_013.c:7758). `MechWeapon::UpdateTargetState` (`FUN_004b9bdc` [T1]): `targetWithinRange =
+dist < (1 − hostZoneDamage) × weaponRange`. The 0x388 WRITER is in the same un-exported gap.
+**Port status: RECONSTRUCTED + runtime-verified (tasks #36/#39/#58) [T2].** The chain: the
+cockpit eye inherits the twist AUTHENTICALLY through the draw traversal (`Torso::PushTwist` →
+hinge `rotationAmount` → `HingeRenderable::Execute` multiplies the live hinge into the matrix
+stack; the eye executes under `jointtorso → jointeye`; verified `[eyefwd]` sweeps with the real
+jointtorso — NO explicit eye-side compose exists, one briefly added on false "frozen eye"
+probe readings double-rotated the view and is retired, see [[cockpit-view]]); the crosshair sits
+at screen center (`gBTAimX = 0` — the old `BTTwistToReticleX` slew was THE bug: the camera
+already yawed, so the crosshair counter-slid to HULL-forward, "twisting leaves the crosshairs
+behind"; `BT_AIM="x y"` still pins it for headless tests) → `BTGetAimRay` (the ACTIVE eye
+publishes pos+basis via `BTSetAimCamera`, leveled in pitch, the twist yaw riding in the basis) →
 `Mech::PickRayHit` (world ray → local frame → `BoundingBox::HitBy` slab test vs the collision
 template's ExtentBox → world hit point).