#45/#134 authentic score/death report tail -- replaces the scoring stand-ins

Reconstructs the dark-gap tail of Mech::TakeDamageMessageHandler
(@0x4a02f4-0x4a0890, raw disasm): the three id-0x16 score reports (kill to
the shooter's player / type-0 wire-fidelity / received to the victim's
player) and the BT 0x38-byte VehicleDeadMessage extension {killed-by player,
kill zone} dispatched from the death tail.  Retires BTPostDamageScore /
BTPostKillScore and the per-hit inflicted credit (never existed in 1995:
@0x4c0200 is bound in no handler-table entry -- byte-scan receipt in
decomp-reference).  Suicides now dispatch and the handler negates the award
(the #134 panic penalty).  Collision divert falls through to the death tail
per @0x4a0375 (wall deaths respawn + blast; no score).  ScoreMessage fields
renamed to decoded truth (vitalHit/zoneIndex/subsysID) + wire asserts;
console VTVDamaged points_transfered corrected (Round(award), not Now()).

Benches: scorekill.sh cross-node kill (kills=1 award=4.88, killedBy=2:1
zone=3, single death cycle), scoreself.sh suicide (type=2 award=-39.00
kills=0), deathblast2.sh re-verified (72 bursts at ~9u).

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

context/combat-damage.md

@@ -391,7 +391,7 @@ zones — mid-fight darkening DOES accumulate when mechs live long enough.
 **Field logs confirm dominance**: Rajel's night-9 log alone has 12 bay-fire events (LRM10
 455-490 pts); ConnMan 10; the "salvo barely dented my armor" reporter was dying to their OWN
 cook-offs. **The real lever is HEAT** (bay fire arms at the bin heat-watcher's FAILURE level;
-the [[heat-and-coolant]]/#96 too-hot economy arms it constantly) plus player training: EJECT
+the [[subsystems]] heat/#96 too-hot economy arms it constantly) plus player training: EJECT
 **hold** purges the burning bay (`DumpAmmo` → "bay fire EXTINGUISHED"); pod players were
 manual-trained to purge ([[pod-hardware]] §Manual), testers are not. Novice sim gates also
 suppress the whole path ([[experience-levels]]).
@@ -569,7 +569,9 @@ percent tables, MadCat) — see #73 on the tracker.
 ## layers are now fixed and live-verified
 The recovery: the un-exported gap held `Mech::TakeDamageMessageHandler @0x4a0230` (found via the
 Mech **message table @0x50bdf8** — rows `{id, name, handler}`: 0x12 TakeDamage, 0x14 PlayerLink,
-0x15 RealMaxSpeed, 0x16 BalanceCoolant, 0x17/0x18 Set/ClearBurningState, 0x19 EjectPilot @0x49f854,
+0x15 RealMaxSpeed, 0x16 BalanceCoolant, 0x17/0x18 Set/ClearBurningState (⚠ label/body mismatch:
+the 0x17 handler @0x49f674 randomizes position + graphicAlarm(2) + re-enables sim — not burning;
+possibly a shifted name row, cf. the factory ClassID mislabels — open-questions), 0x19 EjectPilot @0x49f854,
 0x1a DuckRequest @0x49fa00) and the **crit-chance roll `@0x4a0164`**:
 `p = clamp(0.7·damageLevel² + 0.01, 0..1)`, gated on the player's `simLive` flag (+0x25c — novice
 never crits), rolled per BURST on the current zone (skip if the zone is already burning). The
@@ -582,12 +584,58 @@ entirely — multi-burst under-applied (burst-1)×) is superseded. `MechSubsyste
 @0x4ac0bc` is real (zone damage → destroyed alarms → **vital-subsystem kill**: owner
 `graphicAlarm` level 9, the #28 machinery — CLASSMAP's "HandleMessage@4ac0bc" was a mislabel).
 Live-verified: `[subarmor]` shows parsed scales at spawn; `[critroll] zone=3 -> Myomers subLvl=1`
-— a full chain crit destroying a subsystem. Still deferred [T4→documented]: the `damageType==0`
-COLLISION divert (@0x4a0368 → `0x49ffcc`, its own distribution) and the **id-0x16 damage/kill
-reports** to shooter+victim players (@0x4a04da-0x4a07b2 — the authentic stats plumbing, feeds #45:
-`{tally, zone, destroyed-flag, inflicting subsystem, victim name}`, kill-flagged variant on newly
-disabled, plus a killed-by block gated on movementMode 9/10). Diags: `BT_CRIT_LOG` (`[subarmor]` +
-`[critroll]`), `BT_DMG_LOG`.
+— a full chain crit destroying a subsystem. The `damageType==0` COLLISION divert (@0x4a0368 →
+`0x49ffcc`) and the id-0x16 report tail are BOTH reconstructed — see the next section. Diags:
+`BT_CRIT_LOG` (`[subarmor]` + `[critroll]`), `BT_DMG_LOG`.
+
+## ✅ THE AUTHENTIC SCORE/DEATH REPORT TAIL (2026-08-05, #45/#134) [T1 raw disasm, T2 both benches]
+The rest of `Mech::TakeDamageMessageHandler` (@0x4a02f4-0x4a0890, dark-gap raw disasm) is now
+reconstructed: `BTMechPostCombatReports` + `BTMechPostVehicleDead` (btplayer.cpp), called from the
+handler at the binary's exact positions (mech.cpp). Retires `BTPostDamageScore`/`BTPostKillScore`.
+
+**Entry sequence** [T1]: gyro bounce → death-edge latch `[ebp-0x10]` (was-destroyed at ENTRY —
+before the divert!) → `lastInflictingID` stamp (mech+0x43c ← msg inflictor) → shooter resolve
+(registry find → `shooter+0x190` = shooter's PLAYER; victim's = `mech+0x190`) → **collision divert
+JUMPS TO THE DEATH TAIL** (@0x4a0375 `jmp 0x4a07b5`, NOT a return — a wall/fall death still posts
+VehicleDead + blasts, but skips the score blocks: collision deaths credit no one). Our old early
+`return` here was a latent "wall-death strands the pilot" hazard, fixed with the move.
+
+**The three id-0x16 reports** (all `Player::ScoreMessageID` 0x16, sizeof 0x3C — layout in
+btplayer.hpp, static_assert-locked; `scoreAward`=APPLIED tally in all three):
+- **A @0x4a04da, newly destroyed** → type 2 KillScore to the SHOOTER's player. Basis (+0x24) =
+  the VICTIM role's `killBonus` (role+0x1c). senderMechID = the victim. Suicide (eject charge,
+  self-damage) IS dispatched — the handler negates the award (@0x4c03ab `fchs`) and skips
+  `killCount++`: **the #134 panic penalty, live** (bench: `type=2 award=-39.00 kills=0`).
+- **B @0x4a05d9, not newly killed && tally≠0** → type 0 to the shooter. The ONLY registered 0x16
+  receiver Verify-rejects type 0 → 1995 folded an UNINITIALIZED stack float into the shooter's
+  score on every non-lethal hit (real 1995 bug — @0x4c0200, the handler that accepts type 0, is
+  in NO table entry: dead code). Port sends it for wire fidelity, banks award 0.
+- **C @0x4a06c0, tally>0 (kills included)** → type 1 DamageReceivedScore to the VICTIM's player.
+  Basis = INTENDED damage (burstCount×amount). senderMechID = the INFLICTOR. Feeds the received
+  penalty (`CalcDamageReceivedScore` returns the NEGATIVE) + the operator-console VTVDamaged line
+  (gated `GetConsoleHost()` && !`suppressConsole` — which is why that field is named that).
+Reports carry the LOOP-ENTRY zone (msg+0x24, never rewritten mid-loop), the vital-wreck flag, and
+`inflictingSubsystemID` (msg+0x5c, engine T0 name).
+
+**Score model consequence** [T1]: 1995 pod scoring = **kill awards + received-damage penalties +
+death costs. No per-hit inflicted credit** (the port's old per-hit crediting — and the #95 salvo
+fix on top of it — were inventions riding the dead @0x4c0200 channel; both retired).
+Kill award = `(victimKillBonus + tally) × killerRole.damageInflictedModifier ×
+(victimAvgZoneDamage@0x354 × damageBias + 1.0) × (victimTonnage/killerTonnage)`; same-team kill in
+a non-FFA game = `-friendlyFirePenalty` basis (inline strcmp of `teamName@0x20c`, gate
+`freeForAll@0x250==0`); self-kill negates the whole award.
+
+**The death tail** (@0x4a07b5, shared by the divert): gate = was-alive-at-entry && movementMode
+9|10 → **`Player::VehicleDeadMessage` id 0x17 to the mech's OWN player** — the respawn trigger,
+in the BT 0x38-byte extension `{deathCount -1, dropZone Null, +0x2c killed-by PLAYER EntityID,
++0x34 kill zone}` (bench: `killedBy=2:1 zone=3` cross-node) — then the death Explosion (id 3,
+0x5C, model 0x31; port fires the authored death list from the transition instead, #42) and the
+#89 SplashDamage (re-verified after the reorder: 72 bursts at ~9u). The old mech4
+death-transition dispatch site (which was flagged [T3 sender-undecoded]) is retired — this IS
+that sender. The #55 NULL-playerLink fallback + DEAD_NOTIFY forensics moved into the bridge.
+Benches: `scratchpad/night12/scorekill.sh` (cross-node kill: killer `kills=1 award=4.88`,
+victim respawns, death #1 single-cycle) + `scoreself.sh` (#134 negation). Collision-death tail
+fallthrough is inspection-tier [T3] — shares the benched tail code; field wall-deaths exercise it.
 
 ## (HISTORICAL — the gap as found 2026-07-29, superseded above) [T1]
 The authored crit machinery exists and is reconstructed — `Mech__DamageZone::CriticalHit @0049ccc4`