Note lossy power action maps in ItemTemplate

item_user_power_action and item_power_action are keyed by power, so
rune step tables (repeated powers, multiple power_actions entries) are
collapsed to one entry. Nothing reads the rune data today; the new
RuneTemplate keeps the full lists.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/engine/objects/ItemTemplate.java

@@ -90,8 +90,14 @@ public class ItemTemplate {
     public final EnumSet<mbEnums.DisciplineType> item_disc_res = EnumSet.noneOf(mbEnums.DisciplineType.class);
     public int item_level_req;
     public mbEnums.SexType item_sex_req;
+    // Lossy: some runes list the same power several times with different
+    // arguments (a step table, e.g. PET_DISC). Only the last entry is kept.
+    // engine.parsers.objects.RuneTemplate keeps the full list.
     public final HashMap<String, int[]> item_user_power_action = new HashMap<>();
     public final HashMap<String, Integer> item_power_grant = new HashMap<>();
+    // Lossy: some runes carry up to 35 power_actions entries per power
+    // (a step table, e.g. HNT-031). Only the first entry is kept.
+    // engine.parsers.objects.RuneTemplate keeps the full list.
     public final HashMap<String, int[]> item_power_action = new HashMap<>();
     public final HashMap<mbEnums.ResourceType, Integer> item_resource_cost = new HashMap<>();
     public int modTable;