feedback5 R19D: 5-阿戈尔 revives — the members the battle-start devour knocks out revive once every devour pass is over, by board position (columns from the left, bottom first: the [ASSUMED] reading of the community report's 「左下到右上」), not in knock-out order; later knock-outs take the slots left in time order, uneaten members none (community report relayed 2026-10-07); golden: unchanged

The report's steps 1-2 were verified and hold: the bond HP is on every member before the devour (an elite 深巡,
2904 HP / DEF 655, stands its 4345 from 15 layers on), and each mark is one 5000 物理流失 less DEF (PRTS), so a member
in the middle of a chain is marked by every 阿戈尔 behind it — that is what knocked out the reporter's 蓝蒂 / 小鲨.
Golden unchanged: the corpus's only 5-阿戈尔 battle (bond-egirShip-high, 999 layers) has no devour knock-out.
DESIGN §25.22.5.

docs/research/02-bonds.md

@@ -372,14 +372,14 @@ Members (11 chess, 10 in current shop pool; by tier in shop: {'1': 1, '2': 1, '3
 
 **Implementable spec**
 
-- **[3 distinct]** 阿戈尔 members maxHP x(1 + 0.35 + 0.01*L).
+- **[3 distinct]** 阿戈尔 members maxHP x(1 + 0.35 + 0.01*L) (直接乘算). The members carry it from their deployment, so the battle-start devour finds it (a community report relayed on 2026-10-07: 「第一步给所有鱼加盟约的血量」; an elite 深巡, 2904 HP and DEF 655, stands a mark from 15 layers on — DESIGN §25.22.5).
 - **[3 distinct (battle start)]** Devour (吞噬): see algorithm.
-- **[5 distinct]** The first 3 阿戈尔 members to be knocked out, in knock-out order, each revive immediately on that first knock-out (max_free_respawn_cnt 3; the owner's decision of 2026-10-05, following players' reports — GitHub #105, #140). The battle-start devour's knock-outs count, so the food usually takes them at t = 0 (it stands again, step 4) and survivors = uneaten members + 3. A member takes at most one, on its first knock-out of the battle, however many 阿戈尔 mark it (step 4 cancels its pending marks); a save by its own kit / item / band revive (斯卡蒂's DRE-Y, M3茧甲, 埃芒加德 [ASSUMED for the band]) is no knock-out and takes none. 0.1.3 gave them to the first 3 members by position, fixed at battle start (from PRTS's devour note "从最先部署（更靠左和靠上的）的【阿戈尔】干员开始" and players' videos), so uneaten front members held them.
+- **[5 distinct]** 3 revives (max_free_respawn_cnt), one per member at most, on its first knock-out of the battle; a member never knocked out takes none (the owner's decision of 2026-10-05, following players' reports — GitHub #105, #140). The members the battle-start devour knocks out wait until every devour pass is over, then those still down are revived by board position while slots last — a community report relayed on 2026-10-07, 「第三步是检测左下到右上哪些鱼睡着了给他复活」, read as the columns of the player's own board from the left, bottom first inside a column [ASSUMED; the other reading is the rows from the bottom, left first] (DESIGN §25.22.5). A knock-out later in the fight takes a slot left at once, in time order. However many 阿戈尔 mark a member, it spends one slot at most (step 4 cancels its pending marks); a save by its own kit / item / band revive (斯卡蒂's DRE-Y, M3茧甲, 埃芒加德 [ASSUMED for the band]) is no knock-out and takes none. 0.1.4 gave the slots to the devour's knock-outs in knock-out order; 0.1.3 to the first 3 members by position, fixed at battle start (from PRTS's devour note "从最先部署（更靠左和靠上的）的【阿戈尔】干员开始" and players' videos), so uneaten front members held them.
 - Algorithm:
   1. Order: 阿戈尔 members sorted leftmost first, then topmost ("更靠左和靠上").
   2. Each 阿戈尔 in order marks the unit on the tile directly in front of it (its facing direction) and also the front-tile unit of every 阿戈尔 it has marked (chain). It never marks itself, a unit it already marked, or a unit that marked it.
   3. The marker immediately gains the base ATK of every unit it marked — a 最终加算, added after its ATK percentages (PRTS "该付与来源获得所有标记单位的基础攻击力（最终加算）和阻挡数"; until 0.1.3 the engine added it before them, so a skill's ATK +% scaled it — DESIGN §24.7) — and their block counts.
-  4. After all marks are placed, each mark makes its target suffer one 5000-point physical 流失 (HP loss, source = the target itself; if it dies, the kill is credited to the marker), resolved in marking order. A target knocked out for the first time has its pending marks cancelled ("目标首次被击倒后解除自身被付与但还未触发的【吞噬】效果") — also when it is back at once (the 5-tier revive, 不屈's 立刻重新部署, 埃芒加德, M3茧甲), so a revived member is not devoured again. DESIGN §22.3. Only the target's state cancels a mark: a marker knocked out earlier in the pass still resolves its own marks, credited to it (DESIGN §24.7; until 0.1.3 they were dropped).
+  4. After all marks are placed, each mark makes its target suffer one 5000-point physical 流失 (HP loss, source = the target itself; if it dies, the kill is credited to the marker), resolved in marking order — a member in a chain loses one to every 阿戈尔 behind it. A target knocked out for the first time has its pending marks cancelled ("目标首次被击倒后解除自身被付与但还未触发的【吞噬】效果") — also when it is back at once (不屈's 立刻重新部署, 埃芒加德, M3茧甲; the 5-tier revive comes after the last devour pass), so a revived member is not devoured again. DESIGN §22.3. Only the target's state cancels a mark: a marker knocked out earlier in the pass still resolves its own marks, credited to it (DESIGN §24.7; until 0.1.3 they were dropped).
   5. Each devoured unit adds layers to 阿戈尔 equal to its tier (1-6), once per unit per battle.
   6. (5-member tier) Revive is implemented as: when the unit leaves the field for any reason other than being moved, its next deployment has 0 redeploy time and 0 cost (PRTS). Devour layers: each devoured unit adds its tier once per battle (refreshes next round).
 - Formulas: `hpMultiplier = 1.35 + 0.01*L`; `devourDamage = 5000`; `layersPerDevoured = tier of devoured unit`