#87 root cause: the level-crossing zone-record send was missing -- observers never saw damage

The binary's effect watcher (FUN_0042aa2c) raises
ForceUpdate(DamageZoneUpdateModelFlag) when a zone's damageLevel CROSSES a
band-descriptor threshold (FUN_0042a5f4, master-gated on entity+0x28 & 0xc)
-- that send is how every other pod's replicant learns zone levels
mid-fight. The port's band hub kept only the graphic-state branch, so an
observer's copy sat at 0.0 until destruction: no enemy hull darkening, no
doll movement, ever (the night-10 "no armour discoloration" report).

Restored the level branch with the already-reconstructed DescriptorCrossed
(@0042a5f4) + the master gate on both branches (mesh swap still runs on
every instance). 2-node verified: A-side armour watcher pushed 114 level
changes; every replicant peak matched the master's finals to 4 decimals
(dtorso 0.9321 == 0.9321).

Render path cleared separately (gotcha #23 discharged): BT_ARMOR_FORCE 0/1
A/B captures prove the tint renders (hull -> charcoal at 1.0). Solo
perception is the authentic economy: 2-25 pt lasers vs 68-185 pt pools.

Bench: zonewalk.sh node A now carries BT_ARMOR_LOG + BT_SHOT_EVERY (the
standing zone-replication receipt) + digest_walk.py; armorpx.sh is the
force-pair pixel rig.

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

context/multiplayer.md

@@ -70,6 +70,13 @@ emulator** (⚠ `NotationFile::ReadText` expects NUL-SEPARATED lines). [T2]
   console LAUNCH). SIX bugs fixed to get here (dead-reckoner install, replicant-motion DeadReckon,
   master emission threshold, emission gated on RunningMission, the console-must-LAUNCH fact, replicant
   validity). [T2]
+- **Zone-level replication (#87, 2026-08-03):** an observer's copy of a mech learns zone damageLevels
+  ONLY from zone update records, and the master sends those on BAND-THRESHOLD CROSSINGS (binary effect
+  watcher `FUN_0042aa2c`: `DescriptorCrossed` + master gate → `ForceUpdate(DamageZoneUpdateModelFlag)`)
+  plus every graphic-state change — never per hit. Damage messages do NOT echo locally (replicant
+  `Dispatch` forwards to the master and returns). The port had only the gstate branch (observers saw
+  0.0 until destruction); the level branch was restored + 2-node verified (replicant peaks == master
+  finals to 4 decimals). Full mechanism: [[combat-damage]] §Zone-LEVEL replication. [T1/T2]
 - **Wire-format bug class found+fixed:** MakeMessages replicate RAW over TCP, so string payload must be
   INLINE (`char[N]` at the binary offsets), not a `const char*` pointer (garbage cross-pod). Check
   EVERY MakeMessage for pointer payloads. [T2]