feedback5 CB1: DESIGN §25.15 — the community reports of 2026-10-06 on bonds, strategies and items (seven fixed in six commits, five official behaviour, three not reproduced, two owner questions), and the §25 intro line

docs/history/0.2.0.md

@@ -25,7 +25,9 @@ settled (泥岩's 闭锁; 忍冬, 深靛, 阿) → §25.11; release packaging an
 with no Spine model) → §25.12; round 18 — 拟态物质 at the copy cap (GitHub #207), 华法琳's 7 / 14 (GitHub #175, PR #192),
 a merged elite 拉普兰德 as a new one (GitHub #169), the leader pool per player alive (PR #209), the flying lift and two
 model quirks (PR #211) → §25.13; the community reports of 2026-10-06 (the 孤岛风云 prisoners drawn freed, 忍冬's trigger, a
-bounty burned to death by the 活性源石, 枯朽之种 paying a bounty) → §25.14.
+bounty burned to death by the 活性源石, 枯朽之种 paying a bounty) → §25.14; CB1's community reports of 2026-10-06 on bonds,
+strategies and items (the 谢拉格 wind's endless freeze, 埃芒加德's revive as a knock-out, 佩佩's paid refresh, the 炎佑 on the
+medic's slot, 凯瑟琳's offer, the hidden layers on the result card; the official behaviours pinned) → §25.15.
 
 Decisions of the owner: 2026-10-04 — the server stays on plain `node:http` + `ws`, no web framework (§25.1);
 2026-10-05 — the 补位 plan (§25.3); the 自选编队 rules, the collab operators out of the pool, ISW-A refused (§25.4);
@@ -1062,3 +1064,123 @@ fixed (W5AA's commits name every golden scenario moved); two were already fixed
   bounty 使徒 whose seeds leaked sent every seed into 联防 carrying the card — 15 of 16 re-entries paid it again — which
   is the report; on this tree only the 使徒's own leak carries it.
 - Golden: unchanged. Pinned: `test/sim/feedback5-community-pins.test.js`.
+
+### 25.15 CB1 — community reports of 2026-10-06: bonds, strategies, items — `sim/battle/status.js applyStatus` (cold), `content/items/battle.js reviveNow`, `content/bands/battle.js` (埃芒加德), `content/bands/meta.js` (佩佩), `content/tokens.js airTile`, `screens/result.js resultBonds`, `tools/build-data.mjs` (pool_equip_kathe)
+
+Fifteen of the owner's community reports of 2026-10-06 (items 5, 7, 8, 9 / 37, 15, 20, 21, 23, 25, 41, 42, 43, 45, 49,
+50 of the list). Each was reproduced on this tree with a script, checked against the official data (bonds.json,
+items.json, the client's buff templates), PRTS (卫戍协议：盟约 下半/PRTS盟约记录 and its 备注, 术语释义, 特殊机制) and the
+earlier decisions. Seven were real and are fixed in six commits (7 and 8 share one; golden named in each); five are the
+official behaviour (four pinned by tests); three could not be reproduced and need the reporters' cases; two questions
+go to the owner (the order of §25.15.1, a fallback in §25.15.10).
+
+#### 25.15.1 「维多利亚的锁血锤和烛煌的锁血只生效了一个」: both work, one after the other — no change
+
+- **Measured**: 烛煌 (elite) carrying 坚固维式重锤, a lethal hit every 2 s: 倒地 at the first (绝处重燃, a kit `fatal` saver
+  −50), the hammer's lock at the hit that breaks the 6000 barrier while she is 倒地 (`PRIO_REVIVE` −100), death 8 s later;
+  without the hammer she falls at the second. The 蒸汽之心 path (another operator's hammer) behaves the same.
+- **Why it looks like one**: PRTS 备注 「不处于【重燃】状态下，受到足以致命的伤害时，可触发此天赋效果，次数不限」 — the talent takes
+  every lethal hit outside 【重燃】, so the lock only ever shows when she is killed while 倒地. The order — kits' savers before
+  the consumable 不死 — is the documented [ASSUMED] (§21.21, §22.7's 余烬): the official talent fires on
+  ON_BEFORE_TRY_SET_HP_ZERO (buff template blaze2_t_2) and the autochess hammer's template is not in the client's buff
+  data, so no source gives an order. **Owner question**: should the lock take her first lethal hit instead?
+- Golden: unchanged. Pinned: `test/content/feedback5-blaze-hammer.test.js`.
+
+#### 25.15.2 「谢拉格盟约冰冻时间没有随层数正确成长」 and 「…被在无法被任何干员攻击到的地方永控」: a pair of colds becomes the freeze — `sim/battle/status.js applyStatus`
+
+- **Seen**: the 6-member wind (every 25 s, 寒冷 20 + 0.1 × layers s) froze an enemy for the rest of the battle from 51 layers
+  on, wherever it stood (at the gate too), and never below: measured, 60 layers → frozen from 50 s to the end; 40 → never.
+- **Official**: PRTS 术语释义 寒冷 「友方寒冷始终需要两两一对产生友方冻结，持续时间取双方之中最高」; 异常效果 COLD
+  「在特定条件下转变为冻结」 — the pair turns into one freeze (a lone 友方 cold on a frozen enemy needs a partner, unlike the
+  敌方 rule 「…施加的敌方寒冷会变为敌方冻结」).
+- **Cause**: the second cold froze for max(remaining, incoming) (§23.27) and the older cold stayed on, extended to the same
+  length, so the next cold before it ran out — the next gust — froze again.
+- **Now**: on an enemy the pair becomes the freeze and no cold is left; on an operator (敌方寒冷) the old rule stays. The wind
+  alone freezes 20 + 0.1 × L s of every 50 s from 51 layers (60 → 26 s, 200 → 40 s, all of it from 300).
+- [ASSUMED]: a paired cold emits no `statusApplied` 'cold' (the freeze does).
+- Golden: every scenario where a second cold met a cold enemy (the commit lists 35). Tests:
+  `test/sim/feedback5-kjerag-cold.test.js`; `feedback3-cold-freeze` and 灵知 S2 (`kits_t4`) updated. Docs: docs/SIM.md
+  (`cold`), DESIGN §5 (design/engine.md).
+
+#### 25.15.3 「卡西米尔和艾芒加德策略似乎有BUG：像砾和瑕光这种死亡和部署的叠层效果…无法触发」: a 复活 is a knock-out and a free redeploy — `content/items/battle.js reviveNow`, `content/bands/battle.js`, `content/bonds/core.js installEgir`
+
+- **Seen**: with 埃芒加德's 命结之秘, 砾 (<部署时> 卡西米尔 +1, <被击倒时> 不屈 +2) gained nothing from his first three
+  knock-outs and stacked only on the 4th, real death; 瑕光's <部署时> +4 never fired on a revive.
+- **Official**: PRTS 埃芒加德 (and M3茧甲, 阿戈尔) 备注 「“复活”的实现方式为：受益者因移动之外的原因退场时下次部署的再部署时间和
+  费用归零」 — the operator is knocked out and redeployed at once.
+- **Cause**: both 复活 were `fatal` savers that kept the unit standing (a known simplification, §21.20's "not done"): no
+  `death`, no `deploy`.
+- **Now**: `reviveNow`, a `death` hook (M3茧甲 `PRIO_RESPAWN` 13, 埃芒加德 `PRIO_BAND_REVIVE` 12, ahead of 阿戈尔 5 at 11 and
+  不屈 at 10): the knock-out stands (被击倒时 effects, 克莱门莎, 卡莱莎, 不屈's +5 SP …) and the operator redeploys where it
+  lies, free (full HP, SP reset, 部署时 effects, the 卡西米尔 deployment ATK, a new 坚固 lock — `revivedInPlace` is gone).
+  The ctx carries `revivedBy`, so 阿戈尔 5 does not count that knock-out as the member's first (the owner's decision of
+  2026-10-05, unchanged).
+- [ASSUMED]: a revive whose tile is taken spends nothing (as 阿戈尔 5); with both, M3茧甲 answers first (as before).
+- Golden: the battles with M3茧甲 or 埃芒加德 whose operators fell (11, the commit lists them). Tests:
+  `test/content/feedback5-revive-redeploy.test.js`; bands / bonds_core / feedback1f-hammer / op_lessng / op_zuole /
+  docs-consistency updated. Docs: docs/SIM.md (`fatal`, `death`), DESIGN §5 (design/engine.md), docs/PLAYING.md, research 04.
+
+#### 25.15.4 「局内划掉被ban的盟约的实际效果有问题：只在标准模拟中生效」: the drawn bonds are the same in every difficulty — no change
+
+- **Measured**: the drawn set D — 0 core + 1 add-on in 标准, 3 + 4 in 险境 / 绝境 / 终极 — removes only the operators whose
+  every bond is in it (23–25 banned, none in the pool); each drawn bond keeps 2–10 members through their other bond, 标准's
+  one included. Only 标准 also has the mode's static list (the official modeDataDict inactiveBondIdList, 10 bonds that never
+  activate, §21.7).
+- **Official**: 帮助 「…以及不完整的盟约与不会进入调配池的干员」, the briefing badge 「部分盟约所含干员阵容不完整」, the
+  strategies' 「在<X>部分干员缺席时体验可能不完整」 (research 01 A2). The briefing legend already says it.
+
+#### 25.15.5 「佩佩策略的特殊刷新也是要花钱的，不是免费」: the special refresh is paid — `content/bands/meta.js`
+
+- **Seen**: reaching shop level 2 / 4 / 6 granted a free refresh; the special one cost 0.
+- **Official**: 博学多通 「获得1次特殊刷新」 names no 免费 (德克萨斯's trait 「获得1次免费刷新」 does); the blackboard's `price`
+  0 had been read as its price.
+- **Now**: the level-up marks the next manual refresh special — the usual refresh price, the chess slots filled with
+  <萨尔贡> first. [ASSUMED] `cnt` / `price` 0 change nothing. Golden: unchanged. Test: `test/content/bands.test.js`.
+
+#### 25.15.6 「独行这种盟约是不能叠层的」: they stack, the game never shows them — `screens/result.js resultBonds`
+
+- **Official**: PRTS 盟约记录's header 「下述盟约中部分盟约不会显示叠加层数，但是叠加层数的特质/策略/装备等效果仍然对其生效」 — the
+  four bonds.json `noStack` bonds (调和, 协防干员, 独行, 绝技) take layers like every other (GitHub #139's answer, 0.1.4
+  PR #66); their effects do not read them. The report asks for what the game does not do.
+- **Now**: the one place still printing the hidden count — the result card (「独行 24」, ranked by it) — shows no number and
+  does not rank by it, as the bond strip since PR #66. Golden: unchanged. Test: `test/ui/feedback5-result-bonds.test.js`.
+  Docs: docs/PLAYING.md (层数), research 02 §2.2.
+
+#### 25.15.7 「Touch策略给的医疗干员会跟炎盟约的炎祐冲突，无法同时出场」: the 炎佑 keeps off the map-character slot — `content/tokens.js airTile`
+
+- **Seen** (every season map): on 战场#08 涨潮控制 (always) and 战场#07 排气格栅 (the second 炎佑 of 9 炎) the 外勤医疗 medic /
+  Touch never stood.
+- **Cause**: both spawn at battle start; the 炎佑's tile (void tiles nearest the half's centre) took (10, 2), the medic's
+  stage slot (stages.json `mapChars`), first. The 联防 maps have no predefined medic in the official levels: none there.
+- **Now**: `airTile` holds the map characters' positions. Golden: unchanged. Test: `test/content/feedback5-yanyou-touch.test.js`.
+
+#### 25.15.8 Not reproduced — 「炎祐能错误的被空中单位阻挡」 (item 25), 「选pith策略的时候阿戈尔在联防时会出现加成被清空」 (item 41), 「源石溶剂在干员血量满的时候没生效」 (item 42) — no change
+
+- 25: the 炎佑 never blocks (block 0) and is never blocked (only enemies are block candidates), as PRTS 特殊机制 我方单位
+  「敌人类我方单位不会被角色类单位阻挡」; it hovers on the top-aggro enemy, and an unblocked ranged enemy — a flyer included —
+  stands for each attack (GitHub #58), so a flyer shooting it looks held.
+- 41: Pith's 盟约·辅助干员 (调和) with four 阿戈尔 (5 with 调和's +1): the same 阿戈尔 HP bonus in the normal battle and in 联防,
+  one or two helpers, either half; the 联防 input is the normal one plus the round's layers, HP ratio, SP and 倒地.
+- 42: from full HP the drain ticks 60 / s and ATK +40 % holds. Noted for the owner: the official `periodic_damage` template
+  has `_ignoreForSp: true` (no 受击 SP), while §21.12 lets it charge 受击回复 SP.
+- The reporters' cases (operators, items, screenshots) are needed.
+
+#### 25.15.9 「凯瑟琳装备池没有超出商店等级的装备」: the 凯瑟琳 offer is every shop item — `tools/build-data.mjs`
+
+- **Seen**: the 1 → 2 upgrade offered tiers I–II only (40 seeds: 55 × I, 65 × II).
+- **Official**: the pool is server-side; the players' first-hand account 「原版凯瑟琳1升2都能有6本装备」.
+- **Now**: `pool_equip_kathe` is every shop-eligible item, uniform [ASSUMED] (40 seeds: I 9 … VI 24); data/choices.json
+  rebuilt offline (only that pool's `maxTier` gone). Golden: coop4-ABYSS-7. Test: `test/match/feedback5-cathy-pool.test.js`.
+
+#### 25.15.10 The official behaviour, pinned — 「寻呼模块和电话对干员缪尔赛思用不会给缪尔赛思」 (item 45), 「炎祐能吃到掉血道具的效果」 (item 49), 「两个空弦转职阿戈尔…最后面的空弦不能吃前面的空弦」 (item 50) — no change
+
+- 45: 「电话」 is 简易通讯机 (its phone icon; 备注 「获得的干员等阶不高于当前调度中心等级」), like 寻呼模块 「（不高于当前调度中心
+  等级）」. 缪尔赛思's only bond is 调和, whose only operator in the pool is her, tier VI: below shop level 6 nothing qualifies
+  and the item is used up (as 拟态物质 at the copy cap, §25.13.1); at 6 she comes. **Owner option**: a fallback to any tier
+  when nothing qualifies (what the reporter expects).
+- 49: PRTS 源石溶剂 备注 「携带后，全场范围内的所有敌人类我方单位也会获得此装备的“每秒受到60真实伤害”效果」 — the 炎佑 is one
+  (600 HP in 10 s, no ATK bonus).
+- 50: two operators made 阿戈尔 by 变形同构体 + 阿戈尔重刃 (two 空弦, 空弦 + 哈洛德) devour like any others, through the real
+  intents too (+3 layers, ATK, block). Two NORMAL copies of one item merge (the official rule), so two 空弦 need a normal
+  and an 进阶 set; and the pair counts once toward the 3 members.
+- Pinned: `test/content/feedback5-cb1-pins.test.js`.