HUD: missile/AC weapon pips blink on fire again -- read authentic WeaponState (attr 0x1C)

Reported: the reticle's missile pips no longer momentarily disappear when
firing.  Traced it: the pip's 'loaded' flag has read MechWeapon::rechargeLevel
(>= 0.999) since the reticle Execute was recovered (task #37).  That's a port
APPROXIMATION of the binary's authentic attr 0x1C (WeaponState @0x350).  It
works for emitters -- rechargeLevel is charge-driven and tops off at 1.0 when
Loaded -- but projectile weapons (MissileLauncher/autocannon) never write
rechargeLevel (it's authentically static at 1.0; the recharge DIAL draws full
and never moves).  So a missile pip's 'loaded' was permanently true and the pip
never blinked.  NOT an audio regression -- it never worked in the port; the
audio wave (ea85554) is actually what made the projectile fire-cycle state
(weaponAlarm Loaded/Loading/Firing) correct, i.e. the very signal the pip
should have been reading.

Fix (faithful to the binary): the pip now reads attr 0x1C = the weaponAlarm
StateIndicator level (new MechWeapon::WeaponStatePtr -> GaugeAlarm54::LevelPtr)
and compares it '== stateConst2' -- the loaded constant (2) the binary itself
already stores in AddWeapon (param_10).  The state cycles
Loaded(2)<->Firing(0)/Loading(3)/Jammed(5) for BOTH weapon families, so every
pip momentarily drops on fire.  The authentically-static rechargeLevel dial is
untouched.

Verified live (Blackhawk solo, BT_AUTOFIRE=1 BT_AF_MISSILE=1): both SRM6
missile pips toggle loaded 2<->0/5 on each salvo (emitter pips unchanged);
game boots + runs clean.  KB: context/gauges-hud.md pip entry corrected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

context/gauges-hud.md

@@ -195,10 +195,19 @@ and every instrument is now live [T2]:**
   rotated frame: 0.05-unit attack-direction marks, fresh <2 s red, expiring at 6 s, 1 s blink tick.
   Port feed: the player's TakeDamage handler pushes the impact direction.
 - **Pips** (composed into subB6, master-called): hidden when the weapon's DAMAGE state == 1
-  (destroyed, attr 1); LIT (A) when the FIRE-CYCLE state == 2 (loaded, attr 0x1c; port source
-  rechargeLevel ≥ 1) else dark ring (B, charging); filtered by `weaponMode & elementMask&0xF`
+  (destroyed, attr 1); LIT (A) when the FIRE-CYCLE state == 2 (loaded, **attr 0x1C WeaponState**
+  @0x350 == 2) else dark ring (B, charging); filtered by `weaponMode & elementMask&0xF`
   (the weapon-GROUP bits Front/Rear/Left/Right). **Range plays NO part** — Execute never reads
-  the stored TargetWithinRange slots.
+  the stored TargetWithinRange slots. **FIX 2026-07-18 [T2]:** the pip's "loaded" was a port
+  approximation reading `rechargeLevel ≥ 1` — correct for emitters (charge-driven) but
+  **statically 1.0 on projectile weapons** (MissileLauncher/autocannon never write it — see
+  §Launcher-panel above), so missile/AC pips were **permanently lit and never blinked on fire**.
+  Now reads the AUTHENTIC attr 0x1C = the weaponAlarm StateIndicator level (`WeaponStatePtr` →
+  `GaugeAlarm54::LevelPtr`), compared `== stateConst2` (the const the binary itself stores in
+  AddWeapon). The state cycles Loaded(2)↔Firing(0)/Loading(3)/Jammed(5) for BOTH families, so a
+  missile pip now momentarily drops when fired, exactly like the emitter's. Verified live
+  (Blackhawk, `BT_AUTOFIRE=1 BT_AF_MISSILE=1`): both SRM6 pips toggle 2↔0/5 on each salvo. The
+  authentically-static `rechargeLevel` recharge DIAL (§Launcher-panel) is untouched.
 - **Lock ring** = subB9 (ring+cross) at frame centre, **SPINNING 4°/frame** while the Lock attr
   (0xA) is up. The Lock PRODUCER is the authentic HudSimulation rule (part_013.c:5619-5634 [T1],
   wired task #38): lock requires a target AND your own HUD's host zone damage < **0.75** (a