re: withdraw the "turrets don't move" hedge — Turret is a craft, not a ship mount

The user pointed out that the "Turret" enemy of the first few missions is its
own craft type and must not be confused with the AA turrets mounted on capital
ships. The tables agree, and I should have checked them before hedging:

  UN_e007_ADAN_Turret      AI_ADAN_CraftSquadron_Rookie x70, _Veteran x19
  UN_e007_ADAN_Turret_EX4  AI_ADAN_CraftSquadron_Ace x4

No *_Turret unit ever uses AI_Structure, which is reserved for the things that
genuinely do not move -- asteroids, FloatingMine, SchlosBase, TransitPlatform,
SpaceFortress. AI_ADAN_CraftSquadron_* is Type=Squad in AIParams with the full
manoeuvre-weight block. The distribution matches "first few missions" too: 93
turret members across S01-S06, then nothing until S27.

This retracts the caveat on the 10-of-116 result. Removing it makes that
evidence stronger rather than weaker: the 106 inert records cannot be dismissed
as immobile scenery, because Stage 02's turrets are craft that should be
manoeuvring. The pre-allocated-roster reading survives a test it had been
allowed to dodge.

Lesson recorded in the doc: do not infer a unit's behaviour from its English
name -- check its AIID. The roster is self-describing and the answer was already
in the dump committed two iterations ago.

docs/re/BACKLOG.md

@@ -322,8 +322,11 @@ search cannot find a *schedule*.
   ❔ Still unmeasured: whether the timetable's `t` is frames or seconds.
 * 🔴 **Diffing inside the 116 records did not find the arrival flag**
   (2026-08-24, same doc). 10 of 116 records are dynamic, 106 never change a byte
-  in 170 s — more support for the pre-allocated roster, though turret-heavy S02
-  means "inert" ≠ "not arrived". No field transitions in groups of 3 at the
+  in 170 s — more support for the pre-allocated roster — and STRONGER than
+  first written: the "turrets don't move" hedge was withdrawn after the user
+  pointed out that early-mission "Turret" is a craft type, which the data
+  confirms (`UN_e007_ADAN_Turret` flies under `AI_ADAN_CraftSquadron_*`, never
+  `AI_Structure`). Lesson: check a unit's `AIID`, not its English name. No field transitions in groups of 3 at the
   predicted times. **Blocked on two of my own defects**: the record→unit-ID
   label resolved to `?` for all 116 (reuse `unit_discover.py`, do not re-derive),
   and `RECLEN=0x200` was assumed, not measured — the busiest fields sit at the