Read out of the jar: it is declared beside `getBattleForceClass`, `getAlphaStrikeHeat` and `getAlphaStrikeHeatDamage`, it returns Alpha Strike damage points, and that is why `averageDamage` multiplies by ten. So every cluster weapon's damage is read out of a conversion this project rules out of scope, and the Clan zero is a symptom. The resolving handler answers direct fire exactly - a Medium Laser 5, an AC/20 20, matching Alpha Strike - and answers a Narc correctly at 0 where the cluster table says 2. A rack needs one number the handler will not give statically, the hit count. So #270's fill is a bridge rather than a cure, and the epic says so. Also: jmm confirms the TAC confirmation is the ordinary critical table, which this term already multiplies by, so `TAC_CONFIRMED` stays 1.0 and no constant changes. The centre-torso default is recorded; it does not touch a count.