diff --git a/context/gauges-hud.md b/context/gauges-hud.md
index 8a19c7c..e9dc3cb 100644
--- a/context/gauges-hud.md
+++ b/context/gauges-hud.md
@@ -349,6 +349,15 @@ buttonGroup[btn].GetMapState (table DAT_00518eb4 PE-recovered); the regroup MECH
 Degradation/Failure temps are fixed markers; AmbientTemperature 300; CoolantMassLeakRate 0 on a
 pristine mech (damage-gated); cmArmor/cmCrit all-green (undamaged solo player — BT is PvP-only);
 RANK 1 solo; MessageBoard empty (no status messages exist in bring-up).
+**A heat-FAILED weapon goes DARK with no lamp — authentic (2026-07-23, closes the #30
+remainder) [T1 + T2 field-captured]:** `BallisticWeaponCluster::Execute` @004c9a38 reads exactly
+one weapon-state check — `jammed = (weaponAlarm@0x364 == 5)` for the BTEJAM lamp; its only other
+reads are the bin's cook-off lamp/countdown (`bin+0x18C`/`+0x190`).  Weapon state 7
+(unavailable: FailureHeat / destroyed / mech-disabled / bay dry) has NO presentation — dial at
+zero, everything dark.  Field capture: a solo pilot's right SRM6 tripped FailureHeat
+(`gate1: failHeat=1 heatLvl=2`) and "just stopped working, no indication" — reported as a bug;
+it's the binary's behavior.  Recovery: an EJECT tap revives a FailureHeat 7 while rounds remain
+([[decomp-reference]] §message-tables EjectAmmo).  The jam lamp lights ONLY for a true jam (5).
 **CORRECTION (task #10, 2026-07-11):** the old "Heat MFD is authentically NEAR-STATIC /
 currentTemperature ~77 rounds to zero" claim was computed at the DEGENERATE bring-up heat scale.
 At the authentic 1e7-unit economy (tasks #9-#10) the Heat MFD is fully dynamic: weapons run