Feature(Mythic+ Tools): mplus run summary

[JuJuFX-dev]

What does this PR do?

Adds a Run Summary to Mythic+ Tools: an end-of-key overview panel with one row per party member, plus a per-character history of finished runs. It is off by default and lives on a new "Run Summary" page in the Mythic+ Tools options.

The header shows the dungeon, key level, completion time against the timer, the upgrade or depletion, and total deaths with time lost. Each row shows the spec icon, the class-coloured name with item level, the M+ score with the gain from this run, the looted item, DPS, damage taken, interrupts and deaths. The best DPS and the lowest damage taken are highlighted in the accent colour. Every column except the name can be switched off.

The panel opens once the run's rewards arrive or the loot window closes (Show After Looting), or when leaving the instance if neither happens, and can be reopened at any time with /ov (/ov 2 for the second most recent run, /ov preview for the sample run). A picker in the header switches between the stored runs, listed by dungeon, key level and the local time and date they were played, which are kept per character (5 to 50, default 20) and pruned when a dungeon leaves the season pool. The panel is moved by dragging its header, and Show Preview on the options page opens a sample run so the layout can be checked without running a key.

Where the data comes from, since the combat log is gone in Midnight: the run itself from C_ChallengeMode.GetChallengeCompletionInfo, and damage, damage taken, interrupts and deaths from Blizzard's own C_DamageMeter Overall session, diffed against a sample taken at key start so the figures are right whether or not the Damage Meters module is loaded. Those meter rows stay classified for a while after combat ends (under the Combat or the ChallengeMode restriction), so after completion the run keeps settling until the player leaves the instance: the harvest and the late score push are retried on ADDON_RESTRICTION_STATE_CHANGED, PLAYER_REGEN_ENABLED, CHALLENGE_MODE_MEMBER_INFO_UPDATED and LOOT_CLOSED, and PLAYER_ENTERING_WORLD closes it out. There is no API for another player's score delta, so party gains are the rating summary sampled at key start subtracted from the one after; your own gain is the server's exact value. Item level and spec come from an inspect queue that chains on INSPECT_READY, restarts when a pull ends, keeps going at the chest where the group is out of combat and in range, and rotates by fewest attempts so one player out of range cannot block the rest. Loot is collected from CHALLENGE_MODE_COMPLETED_REWARDS, ENCOUNTER_LOOT_RECEIVED and CHAT_MSG_LOOT together; note that the generated docs describe ENCOUNTER_LOOT_RECEIVED arguments 5 and 6 as itemName/fileName, but BossBannerToast.lua binds them as playerName/className, which is what makes other players' loot readable. Only equippable epic items count as loot; keystones, quest items, housing decor and reagents are skipped. Deaths come from the meter's Deaths type, which returns one row per death rather than a count, so rows are counted per player.

Run records live in a new per-character SavedVariable, EllesmereUIMythicRunsDB, rather than the profile DB, since profile data is exported, imported and stripped as settings.

How was it tested?

Tested in-game on live across several Mythic+ keys: all columns populated for the whole group, including other players' loot, and the history, picker, preview and options behaved as described.

Screenshots

Summary:

Optionpanel:

Checklist

• New settings default OFF (no behavior change without opt-in)
• Zero cost while disabled: no events registered, no polling, no hooks doing work, no frames built
• Cheap while enabled: event-driven (no polling, no timer-based logic, no per-frame allocations)
• No writes onto Blizzard-owned frames (weak-table pattern used); HookScript/hooksecurefunc only, never SetScript on Blizzard frames
• Tested in-game on live; no version gates or pre-Midnight APIs added