fix(rules): duplicate summons get disambiguated ids - the engine now counts id occurrences (seeded from the deployed roster) and gives each new summon of the same creature a build_states-style suffix (celestial_wolf, celestial_wolf-2, ...), so two summons no longer share one _LiveStats slot (the second summon used to reset the first one's counters and their attrition merged); run_encounter aggregation verified to report each slot separately; runner 'known limitation' comment updated; +4 tests (id split, distinct slots, per-slot attrition, run_encounter aggregate)

2026-09-19 23:13:06 +02:00
parent 4f8a131ba0
commit 5e7436b210
4 changed files with 129 additions and 4 deletions
@@ -196,9 +196,10 @@ def run_encounter(
    # Accumulate whatever ids the engine reports: summoned creatures act in the
    # battle and appear in result.stats, so seeding from the initial states
    # only would KeyError on them. Ids seen for the first time get a fresh
-    # accumulator. Known limitation: two summons of the same creature id share
-    # one engine stats slot (the engine keys _LiveStats by id), so their
-    # attrition is merged, not split.
+    # accumulator. Duplicate summons of the same creature are disambiguated by
+    # the engine the same way build_states does (celestial_wolf,
+    # celestial_wolf-2, ...), so each summoned creature owns its own slot and
+    # their attrition is split, not merged.
    totals: dict[str, CombatantStats] = {}
    transcript: tuple[str, ...] | None = None
    for index in range(runs):