#124 CORRECTION: aimed hull hits resolve the struck dz_* PANEL -- players were right

The 08-03 zone rule (struck SEGMENT's SKL dzone, ALWAYS -> every aimed
torso hit = center torso) was wrong, and era players' pushback caught it.
Byte-level proof: MAD_TOR.BGF zone-tags the hull PER PANEL (dz_utorso x36,
dz_ltorso/rtorso x18, dz_dtorso x16, all four rear panels, searchlight);
the dpl hit result kept GEOGROUP granularity (dplHitGeoGroup, T0); and the
binary's segment->zone map @49db20 has NO runtime caller (raw call-scan:
sole caller = CreateStreamedDamageZone, load time) -- no segment-level
collapse mechanism exists.  Oracle's night-10 'only LCT gets hits' audit
was the BUG's fingerprint, not the pod's design.

Fix: MechSegmentPick attributes the struck triangle to its draw op (index
range) and takes the op's .DZM-bound zone -- the #87 armour-darkening
bindings, the same authored patch->zone mapping that already paints the
panels -- with the segment dzone as the untagged fallback.  ZoneAimPoint
now aims hull zones at their patch CENTROIDS (all hull zones previously
shared the chest cull-center), which also upgrades the zone walker.

Bench (2-node zone-walk vs spinning madcat, zonewalk_madcat.sh): every
hull panel resolves individually -- utorso 11/12 in-zone, no L/R
mirroring, all four rear panels register; misses are the panel facing the
shooter mid-spin (correct geometry, not misattribution).  Victim applied
254 hits spread across every panel family.  Was 102/102 hull aims ->
dtorso before the fix.

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

context/combat-damage.md

@@ -102,21 +102,27 @@ the DCS = the struck SEGMENT → its `dzone` (the SKL segment→zone map, `GetSe
 `targetDamageZone`. The cylinder lottery (STEP 6) was only ever the UNAIMED path. The port's
 whole-mech box pick + "STEP-6 zone under the boresight" funnels AIMED fire through the unaimed
 lottery — which is exactly the night-6 report (#73): aim at the arm, get the spray.
-**COMPLETED 2026-08-03 (#124, the zone-walk matrix): the pick is now TRIANGLE-ACCURATE and the
-zone rule is settled against the authored skeleton [T0 data + T2 matrix].** The sphere
-approximation measurably mis-picked (aim dead-on dtorso -> picked rgun/ruleg; its own comments
-admitted a foot could be unhittable behind its own knee) — `MechSegmentPick` now runs a sphere
-PRE-FILTER then Moller-Trumbore nearest-hit over the threaded segments' posed meshes (CPU
-triangle cache from each object's own BGF buffers, `BTGetPickMesh`).  **The zone is the struck
-segment's SKL dzone, ALWAYS**: the madcat's pickable skeleton authors 18 segments — hip,
-shoulders, guns, thighs, knees, ankles+toes, and ONE hull piece (`jointshakey` -> dtorso).  No
-ltorso/rtorso/utorso/rear/door/searchlight segments exist, so aimed fire at any torso panel
-authentically designates CENTER TORSO — the side/rear/upper panels strip only via the UNAIMED
-path (missiles/splash/rams through the cylinder).  A brief shared-carrier->cylinder override was
-an embellishment and was removed same-day.  Final matrix (two-node, spinning target, servo
-walker): limbs 55/70 in-zone (legs/feet 6/6), hull-family aims -> dtorso 56/69, victim
-consumption matching.  **The night-10 field audit table is this model's fingerprint** — 'only
-LCT gets hits' from aimed energy IS the pod's design.  Bench: [[test-harness]] §zone-walk.
+**COMPLETED 2026-08-03 (#124, the zone-walk matrix): the pick is TRIANGLE-ACCURATE** [T2 matrix].
+The sphere approximation measurably mis-picked (aim dead-on dtorso -> picked rgun/ruleg) —
+`MechSegmentPick` runs a sphere PRE-FILTER then Moller-Trumbore nearest-hit over the threaded
+segments' posed meshes (CPU triangle cache from each object's own BGF buffers, `BTGetPickMesh`).
+**⚠ CORRECTED 2026-08-04 (field pushback from era players — they were RIGHT): the 08-03 zone rule
+("the struck segment's SKL dzone, ALWAYS" -> every aimed torso hit = CENTER TORSO) was WRONG.**
+The authentic rule: **the pick's zone is the struck PATCH's authored `dz_*` tag** — the art
+zone-tags the hull PER PANEL (`MAD_TOR.BGF` carries `dz_utorso`×36 / `dz_ltorso`×18 /
+`dz_rtorso`×18 / `dz_dtorso`×16 + all four rear panels + `dz_searchlight` across its patches
+[T1 bytes]); the dpl hit result kept GEOGROUP granularity (`dplHitGeoGroup` in the renderer's
+result block [T0]); and the binary's segment->zone map `@49db20` has NO runtime caller (sole
+caller = `CreateStreamedDamageZone`, load-time — raw call-scan [T1]), so no segment-level
+collapse mechanism even exists.  Aimed fire in the pod stripped the exact hull panel under the
+reticle.  The segment-level model looked airtight because LIMBS agree at both granularities (one
+zone per limb mesh) — the collapse only bit the hull, and Oracle's night-10 audit ("only LCT gets
+hits") was the BUG's fingerprint, not the pod's design.  Port: `MechSegmentPick` attributes the
+struck triangle to its draw op (index-range) and takes the op's `.DZM`-bound zone (the #87
+armour-darkening bindings — the same authored patch->zone mapping that already paints those
+panels), segment dzone as the untagged-patch fallback; `ZoneAimPoint` aims hull zones at their
+patch CENTROIDS so the zone walker can exercise per-panel.  Bench: [[test-harness]] §zone-walk
+(madcat variant, scratchpad/night11/zonewalk_madcat.sh).
 **TWIST-SIGN VERIFIED (2026-08-04) [T2 live]:** the frame adapter's inferred angular flip
 (`SelectSlice: theta -= TorsoHeading()`, vs the binary's `+=` before the z-reflection) is
 CORRECT — bench: target torso pinned 0/+140°/−140° (`BT_FORCE_TWIST`, sim-level