fix: include Vulpisfoglia Hunt addition on first damage

docs/history/0.2.4.md

@@ -274,3 +274,22 @@ 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 Vulpisfoglia's first Hunt instance
+
+[PRTS 忍冬](https://prts.wiki/w/忍冬), 追凶's remarks, includes the first damage instance in its arts addition.
+The mode's generated talent blackboard (`chess_char_3_18_a/b`, `atk_scale` 0.3, `interval` 10) supplies the numbers;
+no mode-specific first-hit exception was found. The old callback recorded the first timestamp and returned,
+skipping the addition on every new enemy. Kit hooks are installed before initial deployment, so this was not a
+delayed stat or talent installation.
+
+The callback now records the timestamp and continues to the existing addition path on that same instance.
+The fixed window, damage tags, dodge settings and recursion guard retain their previous behavior; skills,
+modules and other operators are unchanged. Full-content controlled-enemy tests cover ordinary first hits in both
+forms and all selectable modules/skills, first skill damage from S1–S3, per-enemy timing and actual HP/event totals.
+The existing HP-loss conversion regression now expects one rider on every attack, including the first.
+
+The intended golden moves are `roster-007/009/026/039`, `bond-soloShip-low`, `bond-yanShip-low`,
+`coop2-NORMAL-3`, `coop4-ABYSS-7` and `coop2-NORMAL-5-coverage-diy`: the extra first instance changes damage,
+kills and downstream battle/match choices in scenarios that field Vulpisfoglia. Fields, stand-ins and DIY
+scenarios retain their digests.