fix: 外勤医疗预置角色保持初始索敌顺序 (#315)

docs/history/0.2.4.md

@@ -274,3 +274,25 @@ enemy: picking emitted a unit click with no definition, instead of the tile clic
 engine-canvas regression retains the card/100 HP assertions and also covers another field refresh, live HP loss and
 closing the card when the crate is destroyed. Device metadata supplied by the new entry still wins; changing fields
 does not carry old devices across. Gameplay and allied targeting rules are unchanged.
+
+### 29.15 Prepared 外勤医疗 target order (follow-up to #451)
+
+PR #451 made 预备干员-医疗 visible in preparation but deliberately left its initial aggro order unchanged. In the
+user-provided [卫戍协议 recording](https://b23.tv/RQLI8WS), the right-side 联防 board at 19:13 has Touch and 哈洛德
+inside the same flying 守墓石像's attack range when it locks its target, yet the attack selects 哈洛德. The 17:01
+preparation frame shows 哈洛德 with no equipment, and his position makes him the right player's first ordinary
+deployment under the current column scan. The 19:36 clip supplies another targeting comparison. These observations
+support an effective priority earlier than ordinary operators for the prepared 外勤医疗 slot; they do not expose the
+official game's unit identity or exact deployment counters.
+
+The battle sim creates the selected map-character variant at `battleStart`, after deploying the board. [ASSUMED]
+The prepared slot retains an earlier effective targeting order whether it stays 预备干员-医疗 or is replaced by Touch.
+Only `aggroSeq` gets a negative, pre-initial value; `deploySeq` remains the actual spawn's identity for deployment
+hooks and scheduled effects. [ASSUMED] If several players have prepared slots, their relative order follows the
+existing player order. A map character spawned ad hoc after battle start keeps normal summon order. The real flying
+守墓石像 tests check both variants at target-lock time, a right-side 联防 Touch, and the higher-taunt exception.
+
+`npm run golden:update` recomputed all 287 scenarios. Only `coop2-NORMAL-14-standins` changed: its human seat uses
+`band_amedic`, and combat differences first appear in round 11. The match remains a round-14 victory with team LP 31;
+that seat's final kills move 272 → 273 and leaks 44 → 43. Its boss damage moves 193,091 → 189,876, while the partner's
+moves 586,909 → 590,124. All other golden scenarios retain their prior result.