feedback1 integrate: docs for the batch 6 QA residuals (DESIGN §21.20-§21.25, SIM, META, PLAYING, research 04, CHANGELOG)

The hammer lock per deployment for borrowers and in-place revives (both [ASSUMED] where no source decides), 卢西恩 / 锏
casting for an airborne 蒂比, rule 3 for a summon that is gone, the dispatcher snapshot taken before the first item;
PLAYING and CHANGELOG no longer say every debuff misses an airborne 蒂比 (ground-enemy auras and counters still reach
her); research 04's hammer line says once per deployment. docs-consistency pins it.

docs/META.md

@@ -332,10 +332,11 @@ Dispatch order per player: `global` → `band` → `bond` (data order) → garri
 → equipped items → EffectRefs (insertion order). `onPrice` runs the priced chess's own 特质 first (购买价格为N sets the
 price that 远见's discount and the strategies' caps then act on). Every call is isolated with try/catch (the error is
 logged once and counted in `match.dispatcher.errors`); nested dispatches are capped at depth 6.
-The equipped-items step walks a snapshot (the owned chess and each holder's items as they stand when it begins) and
-runs an item only if, when its turn comes, it is still equipped on that holder and the holder is still owned: handlers
-move and destroy pieces mid-walk (突变细胞 transforms its holder, normal 博士投影 destroys itself), so an item a handler
-took off is skipped and the item after it still runs; a piece gained or equipped meanwhile waits for the next dispatch.
+The equipped-items step walks a snapshot (the owned chess and each holder's items as they stand when it begins: every
+[holder, item] pair, taken before the first item runs) and runs an item only if, when its turn comes, it is still
+equipped on that holder and the holder is still owned: handlers move and destroy pieces mid-walk (突变细胞 transforms its
+holder, normal 博士投影 destroys itself), so an item a handler took off is skipped and the item after it still runs; a
+piece gained or equipped meanwhile waits for the next dispatch, and an item moved meanwhile runs at most once.
 
 ### 2.3 Garrisons (特质)
 The dispatcher calls `handler[hook] ?? handler.run` only on the hook of the garrison's `eventType` (a handler may widen