Ledger House Job — Playtest Log (Simulated Runs)
Two fully-diced simulations (genuine RNG, no survival bias), run back-to-back against the same module, with a set of rules fixes applied to Iron Core and Metal meet Flesh between them (Fear auto-clear on source death, Overwhelming Trauma rewrite, Snake Eyes-in-Clash ruling — see the confirmed rulings below Run 1 in conversation history / commit to the master docs).
Run 1 — Corvin Ashgrave, Wren Ashcombe, Helga Stonewright
Party: Corvin Ashgrave (Bravo/Duelist), Wren Ashcombe (Halfling thief), Helga Stonewright (Dwarf Law priest).
Grave-Warden / Faith math
- Did a PC cast Wrathful Light or Rime-Fang’s Bite? Outcome: No. This roster cannot exercise this test at all — Helga is Law Domain (no offensive Miracle in her list), and nobody else has Faith investment. The flat-2-Impact-can-never-cross-WT4 question needs a Mercy/Healing or otherwise offense-capable Faith build in the party; recommend re-running this specific scene with Perpetua Vane or an equivalent instead of Helga.
- Did Fear Inducing land? What ruling did you improvise? Yes, on both Wren and Helga at the top of the fight. Discovered a contradiction between the playtest doc and Iron Core: the playtest doc claims Fear “has no written way to shake it off,” but Iron Core’s own Conditions list already states Fear clears “by taking the Regroup action when out of sight or has cover from the object/being causing the fear.” That fix may already be in place and the playtest flag is simply stale — worth confirming. Separately, we found the clearance route is close to unusable in this fight’s actual geometry: a single-room strongroom against one melee guardian gives no cover to break line of sight, so even with the rule on the books, players defaulted to just re-rolling Resolve each activation instead of spending a full turn on Regroup. Also improvised: Fear auto-clears when its source is destroyed mid-condition (no RAW answer either way).
The Watch
- Evade, fight, or caught? At which stage? Evaded. The Grave-Warden fight (loud, per the explicit trigger) pushed the Watch straight to Stage 1 (Alerted) the moment it ended. One opposed Stealth check at Difficult (-2) got the party past the only checkpoint we rolled for (Margin +1 — closer than it looked). Never escalated to Stage 2 Pursuit.
- Did Suppressed create real pressure, or fizzle? Never tested — the Watch never got close enough to loose crossbows. Worth a dedicated run.
- Did the Cunning Leader/Fodder-Threat question come up? No — no Watch combat occurred, so Patrolmen never got the chance to spend (or fail to spend) Threat. Still an open rules question.
The Sluice Vault
- Did Drowned feel oppressive, or clear trivially? Never really tested as designed — the dice pushed past Drowned entirely. Wren’s Passive Notice (7, untrained) failed the Aware/Unaware check, and because Unaware targets get no defense roll of any kind against a Hazard Roll, one bad trap roll (14 vs her Wound Threshold 4) skipped Drowned’s slow-burn tension and went straight to Instant Incapacitation (Impact ≥ 3× Threshold). That’s a real finding on its own: a squishy Unaware character facing a Hazard Roll has zero agency in the outcome — not even a bad roll to make. Worth deciding if Unaware targets should at least get some roll (even a heavily penalized one) rather than a flat compare.
- Did the Bog-Wretch ambush land while PCs were still Drowned, or miss the timing? Landed hard — arguably harder than intended, since it hit while the party was mid-rescue of an Incapacitated ally rather than merely Drowned. Surfaced a real gap: this specific three-person roster has no Medicine skill and no healing Miracle at all. The only recourse to Wren’s Bleed-Out checks was two untrained Corvin Medicine rolls (2d6+0) — one failed (Death Mark), one succeeded (Triage/Stabilize) on the second attempt. That’s a coin-flip on a party member’s life with literally no skill investment behind it, which is a party-composition problem more than a system one, but worth flagging: a “playtest party” with zero Medicine/healing is a fragile default to test trauma-heavy scenes with.
The Frost-Cave Troll
- Did a Brace user take a hit? Outcome? Yes — Helga (Block/shield-oriented). Took several hits across the fight; her shield’s SV routinely reduced Impact to 0 or near it, but Overwhelming Force’s automatic 1 Stress on any Block vs. a Large enemy (win or lose) bled her out anyway — she reached Breaking (100% Stress) despite never taking a Wound from a “real” hit, then took her first Wound purely from Stress overflow once maxed.
- Did a Dodge/Parry user take a hit? Outcome? Yes — Corvin (Parry-oriented). Took two real Wounds across the fight (one from a clean Impact ≥ Threshold, one from Stress overflow after a Snake Eyes on defense), and also generated the single most interesting offense of the fight via repeated Riposte triggers.
- Conclusion: universal Elite-durability issue, or Brace-specific? Universal, not Brace-specific. Both defense styles got tagged by the Troll’s attacks, and both hit their own Breaking point independently. The actual bottleneck wasn’t either PC’s defense choice — it was Troll-Blood Regeneration, which healed 1 full Wound Slot at the start of every one of its activations. Across 9 simulated rounds, the party landed real Wounds on the Troll five separate times (several via Corvin’s Riposte, one via a clean Strike) and every single one was healed back before it could compound, because no single hit ever cleared 1 Wound Slot’s worth of net progress in a round where the Troll hadn’t already acted. The only tool that reliably worked around it — Corvin’s Momentum-fueled Surge for a second attack in the same round — needed a second Margin-7+ win in the same round to actually stack two Wounds ahead of the heal, and that only happened by not happening: even with Surge active twice, only one of those attempts crossed the line. No Fire source existed anywhere in this party’s kit, so the Weakness clause (which fully suppresses Regeneration) was never tested at all — this run cannot tell you whether Fire actually fixes the problem, only that without it, the fight can stalemate indefinitely. The scene ended in a full party retreat, not a kill — both melee PCs Broken (maxed Stress) and carrying real Wounds, the Troll effectively undamaged. Recommend deciding whether “retreat as a valid outcome for a Major Scene” is acceptable design intent, or whether Regeneration needs a cap, a cooldown, or a mandatory in-fiction Fire source seeded somewhere in this specific scene if no party generates one itself.
- Any Natural 12 + Margin 12+ double-dip observed? No natural 12s came up across the entire session (Grave-Warden, Watch, Sluice Vault, or Troll fights) — the double-dip flag was never triggered, purely due to dice luck. Re-run recommended before ruling this out.
General — other seams that surfaced
- Wound-slot-capacity ambiguity. RAW (“taking a 4th Wound” for a 3-slot character) only defines Incapacitation as exceeding capacity, never exactly filling it. This came up three times: the Grave-Warden took a Major Wound that filled both its slots exactly (ruled: not yet dead, needs one more hit — and then died to that hit next round); a 1-Wound-Slot Bog-Wretch took its one Wound (ruled: dies outright, since a Fodder’s whole design point is a 1-hit kill and the general rule clearly wasn’t written with 1-slot creatures in mind); Corvin and Helga both later took Wounds purely from Stress overflow at their own cap, which the text does support explicitly. Resolved after Run 1: confirmed as-designed — exact-fill is not incapacitation, only overflow is, uniformly, no Fodder carve-out. See Run 2 for how this actually plays out on 1-slot creatures in practice.
- Snake Eyes has no defined behavior in an opposed Clash. The consequence list (“Gear Degradation / Panic Reflex / Momentum Drain / Catastrophic Exposure”) is explicitly scoped to unopposed checks. It came up three times this session in opposed rolls (once on a Resolve/Fear check, twice in combat Clashes) and each time we improvised a Panic Reflex-style extra Dissonant Stress on top of the automatic loss. Also had to rule whether Finesse’s natural-1 reroll applies to a Snake Eyes double-1 — ruled no, since Snake Eyes’ “regardless of…Gear modifiers” phrasing reads as an explicit override. Resolved after Run 1: written into Iron Core — auto-loss + Panic Reflex, no rerolls ever.
- Overwhelming Force only mentions Block, not Brace or Dodge, against a Larger opponent. Whether that’s deliberate (shields catch more surface area) or an oversight is worth a one-line confirmation — Helga switched from Block to Brace mid-fight specifically to dodge this tax, which worked, but felt like exploiting a gap rather than a real tactical choice. Still open — no rule change made yet.
- Instant Incapacitation (Impact ≥ 3× Threshold) doesn’t say whether it also fills Wound Slots. Ruled it does not — it’s a pure status effect bypass. Result: Wren went unconscious with a perfectly clean 0/3 Wound Slot track, which reads strangely on a character sheet. Resolved after Run 1: rewritten as “Overwhelming Trauma” in Iron Core and Metal meet Flesh — explicitly bypasses Wound Slots and drops straight into At Death’s Door / Bleed-Out, specifically so bonus Wound Slots from gear/spells can never grant immunity to a catastrophic hit.
- A tie on Brace (neither an explicit win nor loss per Brace’s own binary phrasing) was ruled as a no-effect bind, consistent with the general Clash tie rule — but Brace’s text doesn’t actually cover this case. Still open.
Run 1 bottom line
The Grave-Warden and Fear tests were compromised by this specific roster (no offensive Faith caster) and by tight-room geometry (no cover to Regroup away from Fear). The Watch pressure track worked exactly as designed — real tension, no forced fight. The Sluice Vault’s Hazard Roll produced a legitimate, serious finding about Unaware targets having zero agency. The Frost-Cave Troll fight is the headline result: Troll-Blood Regeneration, not Brace vs. Dodge/Parry, is the actual Elite-durability bottleneck, and this party had no way to test the intended Fire-based fix.
Run 2 — Pillit Thistlewood, Uzgar “Ox” Bellows, Perpetua Vane (+ second Grave-Warden)
Party: Pillit Thistlewood (Halfling Ranged Skirmisher, equipped with 2 Naphtha Fire-Flasks), Uzgar “Ox” Bellows (Half-Orc Frontline Anchor, Hardened M6), Perpetua Vane (Human Faith caster, Mercy & Healing, Hardened M8, has Wrathful Light). Deliberately built to plug Run 1’s roster gaps: an offensive Faith caster, a real tank, and a Fire source. The Cold Open was also escalated to two Grave-Wardens instead of one, per direction.
Grave-Warden / Faith math (now testable)
- Double Grave-Warden fight, outcome: Completely one-sided — both destroyed in 4 rounds, zero Wounds taken by any PC (Ox picked up a few Glancing-Hit Stress ticks and nothing more). Real finding: doubling the guardian count barely stressed a Hardened-leaning party. The single Grave-Warden in the module reads as tuned for a fragile Green/Blooded roster (confirmed by Run 1’s much rougher time with just one); a competent Hardened trio shrugs off two without difficulty. Worth deciding whether the Cold Open should scale its guardian count/tier to party Standing, the way the Bestiary’s Enemy Budget table already does for other encounters.
- Did Perpetua cast Wrathful Light on a Grave-Warden? Outcome — the actual answer to the flagged question: Yes, twice this session (once on GW-B, once later on the Frost-Cave Troll). The flat-2-Impact-can-never-cross-WT4 problem does not exist. Wrathful Light, as currently written on Perpetua’s sheet, is a pure Resolve-save-or-2-Dissonant-Stress effect — it never touches Impact or Wound Threshold math at all. The playtest doc’s own framing (“A flat 2 Impact… can never cross it, on any roll, at any tier”) describes a version of the spell that doesn’t match what’s actually on the character sheet today. Either the spell was redesigned since that flag was written (most likely — the flag is simply stale and can be closed), or there’s a mismatch between an intended older design and the current implementation worth a one-line confirmation. Also noted: Rime-Fang’s Bite doesn’t appear anywhere else in the corpus — it may never have been implemented, or was renamed.
- Construct vs. Undead/Daemon/Mutant bonus clause confirmed working as written: Grave-Wardens and the Frost-Cave Troll are both outside Wrathful Light’s “also gains Fear” bonus list (Construct and Beast respectively), so only the baseline Resolve-or-Stress effect applied both times — correctly gated per the Bestiary’s Creature Types list.
- Did Fear Inducing land? Yes, on Perpetua and Pillit (Ox passed). Both cleared it cleanly this run by retreating to cover behind crates/a pillar and taking Regroup — the updated auto-clear-on-source-destruction rule wasn’t even needed here, because the room geometry this time let players use the existing Regroup clearance as intended. Good confirmation that Run 1’s “unusable in a tight room” problem is genuinely fight-specific, not universal.
The Watch
- Same result as Run 1: one opposed Stealth check, another exact tie (9 vs 9) on the same unresolved no-tie-break gap flagged last time — this is now a confirmed recurring seam, not a one-off roll, worth an explicit ruling (recommend: ties favor the fleeing party, consistent with how the module frames the Watch as “evade or outrun, not fought to the death”). A follow-up Acrobatics check (Messy Success) got the party through. Stage 1 held, no Pursuit.
The Sluice Vault (contrasting result)
- Did Drowned feel oppressive, or clear trivially? Genuinely mixed by character this time — a good result. Pillit cleared it in 2 attempts, Ox never needed to try (tanked the Disadvantage instead), and Perpetua failed 3 consecutive Athletics checks and never cleared it the entire scene, taking a cumulative Stress tick every round. That’s Drowned working exactly as “a slow, inescapable drain” should — for the specific character whose dice went cold, without deciding the outcome of the whole scene, which is the fix Run 1’s near-death case couldn’t demonstrate.
- Aware/Unaware outcome this time: Reversed and instructive. Ox — the highest-WT PC (9) — was the one who rolled Unaware, and it barely mattered: a straight Hazard-Roll-vs-Threshold compare with no defense still only produced a Minor Wound. Pillit and Perpetua, both Aware, Braced and took a Minor Wound and a Glancing Hit respectively. This confirms Run 1’s finding was specifically about low-WT-plus-Unaware, not Unaware alone — the same “zero agency” mechanic is much less dangerous when the Unaware character can absorb the raw total safely. The underlying agency gap is still real and still worth workshopping, but it’s a severity problem tied to WT, not a universal one.
- Bog-Wretch ambush: cleanly resolved, two destroyed via Wound overflow (one to a Major Wound exceeding its single slot, consistent with the confirmed capacity ruling), one Stress-broken and Routed via its own Stress-Limit-0 mechanic working exactly as designed.
- Correction made mid-session, logged for accuracy: Fates’ Bounty was briefly misapplied to a Fodder’s natural 12 — the rule explicitly restricts the extra die to “the player (or Elite/boss NPC),” so Grunts and Fodder never get it. Also briefly missed applying a Fodder’s own Stress-Limit-0 break off a Glancing Hit before rolling its next action — caught and corrected in the moment; worth double-checking this specific interaction (Glancing Hit Stress vs. Stress-Limit-0 Fodder) stays front-of-mind, since it’s easy for a GM to resolve the Wound/Impact math and forget the accompanying Stress tick actually ends the fight on its own.
The Frost-Cave Troll (headline result — Fire suppression tested, then corrected)
- Correction, logged for accuracy: the first pass through this scene was run with two bookkeeping bugs — Ox’s Dissonant Stress was wrongly reset to 0 at the scene transition instead of carrying his 7/9 forward from the Sluice Vault, and Winded (-1 at ≥50% Dissonant Stress) was never actually applied to anyone despite both Ox and Perpetua crossing that line. Both were caught by the GM (user), not the dice. Because those errors changed the modifier on almost every roll either character made, the whole scene was re-run from scratch with correct starting conditions — Ox at 7/9 Dissonant (Winded), Perpetua at 5 Dissonant / 2 Locked = 7/9 (Winded) — rather than patching individual results. Everything below is the corrected redo; the paragraph immediately following the bullets after it is what the original (buggy) run had reported, kept for contrast rather than as a finding in its own right.
- Did the Naphtha Fire-Flasks actually suppress Regeneration? Yes, on the second flask — but this run’s dice ran even colder than the original: the Troll beat its Dodge check four times in a row (the first flask’s zone, twice, then the second flask’s own opening check) before finally failing on the second flask’s follow-up check in Round 4. Same headline as before, stated more forcefully by the re-roll: an untrained Dodge (2d6+0) beating a flat TN8 most of the time is a real resource risk for a 2-flask loadout, and this run is a second, harder data point that a bad streak can burn most of the fight’s duration before the plan pays off at all.
- Frenzy + Fire suppression convergence, this time with real stakes attached: once the Troll’s Stress (3/4 from accumulated Glancing Hits) hit +2 from the failed flask and blew past its 4-point limit, Frenzy triggered mid-activation, before the Troll’s already-declared Sweeping Uproot had been rolled — meaning that attack had to be re-rolled with Advantage rather than resolved at its original flat total. That’s a sequencing question worth a GM-facing note: a mid-activation state change (failing an environmental check) can retroactively change how the rest of that same activation resolves.
- This is the corrected version of the “no PC casualties” finding, and it’s the headline: there were nearly two. With Ox and Perpetua both entering the fight already Winded from carried-over Stress, the Troll’s very first Sweeping Uproot (Round 1) pushed both of them to Breaking before either had taken a single action of their own — Ox from a Glancing Hit plus the automatic Overwhelming-Force Stress tax on his Block; Perpetua from paying her own Miracle’s Locked Stress cost (see below). From there the fight ran 8 rounds, not the original run’s ~5: Ox was fully Incapacitated in Round 6 (his 3rd Wound, with no slot left to take it — Blood Frenzy and a lucky Margin-6 Bleed-Out check stabilized him before a Death Mark, but it was close), and Perpetua ended the fight at an exact 3/3 Wound Slots, one hit from the same fate. Pillit — full Stress, never Winded, never touched in melee — landed the fight’s last three meaningful hits, including the actual kill shot, entirely from range while the Troll had nothing left to Dodge with. The corrected bookkeeping turns “no Breather between Sluice Vault and Frost-Cave” from an abstract pacing question (open item #6 below) into the direct cause of a near-death and an actual Incapacitation. That is the real answer to that open item, not a hypothetical.
- New ruling forced by the correction, flagged for confirmation: what does “any further Stress converts to Wounds” at Breaking actually convert at? Iron Core says Breaking turns further incoming Stress directly into Wounds but never states an exchange rate. Ran this session on the only existing precedent in the rules — the Blood Price feat’s explicit 2 Dissonant Stress = 1 Wound rate, applied in reverse — and additionally had to improvise what happens to a single unpaired point of overflow (ruled: it just holds the tracker at the cap rather than rounding up to a wound on its own). This came up five separate times in one fight and directly decided two of the session’s biggest moments (Ox’s Incapacitation, Perpetua’s final Wound). This needs a real, written ratio, not a borrowed one.
- New ruling forced by the correction: paying a Miracle’s Locked Stress cost can trigger Breaking before the Tithe roll resolves. Perpetua’s Elara’s Comfort in Round 1 is the clean example: her 1 Locked Stress payment pushed her total to the cap before the roll, so the roll itself had to carry the Breaking penalty (-2), not Winded (-1) — and it then failed, meaning she spent a resource and a Breaking-tier roll for nothing. This interaction isn’t written anywhere in Iron Core currently and should be, since it changes which modifier applies to the roll a player is about to make, not just its aftermath.
- New open question, deliberately not resolved unilaterally: does a Frenzied (“fights to death”) monster take a free Coup de Grâce on a downed PC instead of fighting an active threat? With Ox Incapacitated in Round 6 and Perpetua still standing, the Troll had a choice the rules don’t clearly settle — a guaranteed kill on the helpless target per At Death’s Door’s Coup de Grâce rule, or continuing to fight the PC still hurting it. Ruled for this session that a Frenzied beast fixates on the active threat rather than a downed one, but this is a real GM-guidance gap: it decides whether “going down” is a stabilize-and-recover state or a death sentence the moment an enemy chooses otherwise.
- Positive finding: Ox’s Blood Frenzy trait (clear 1 Dissonant Stress on taking a Wound) is doing real, felt work as a pressure-release valve against the new Stress-to-Wound conversion, repeatedly pulling him back below Breaking immediately after a Wound landed. Worth noting as a species trait that’s earning its keep mechanically, not just flavor.
- Ruling reconfirmed: the Bestiary’s Frenzy break-behavior “drops all defense” (Block/Dodge/Parry) held again this run and was directly responsible for the Troll going down as fast as it did once triggered — same real ambiguity flagged after the original pass, now backed by a second data point.
- Snake Eyes on a PC, confirmed working the way the new Clash rule intends: Perpetua rolled a natural double-1 on a Dodge against the Troll’s Vicious Frenzy claw in Round 7 — auto-loss regardless of her actual total, plus the Panic Reflex Stress, and it directly produced the Minor Wound that put her at exact Wound-Slot capacity. Good, if uncomfortable, confirmation that the rule bites just as hard against the party as it did against the Troll in the original pass.
- For contrast, what the original (buggy) run reported: Troll destroyed in “exactly 2 more rounds” after the Frenzy/Fire convergence, zero PC Wounds beyond Glancing Hits, and Perpetua “Breaking on her second Wrathful Light of the session.” All three of those were downstream of the uncorrected Stress bookkeeping and should be considered superseded by the corrected run above, not read as a second independent data point.
Run 2 bottom line
This roster answered every question Run 1 couldn’t, and the corrected Frost-Cave Troll redo answered one Run 2 itself got wrong the first time. Wrathful Light’s flat-Impact problem turned out not to exist in the spell’s current form — that flag can likely be closed. The Grave-Warden Cold Open, even doubled, is easy for a Hardened party — worth a Standing-scaled guardian count. The Sluice Vault’s Drowned/Hazard mechanics work as designed once WT and skill investment aren’t both at rock bottom simultaneously. The Frost-Cave Troll confirmed Run 1’s central hypothesis: Fire suppression is the intended answer to Regeneration, and it works decisively — but getting a failed Dodge out of the target isn’t guaranteed, a party without redundant Fire sources can lose their one shot at it to bad luck, and (the corrected finding) going into that fight already Stressed from the scene before it is not a pacing footnote — it is the difference between a clean win and a PC going down.
Open items across both runs
- Overwhelming Force naming only Block, not Brace/Dodge, against Larger enemies — still unconfirmed.
- Brace’s tie case — still unwritten.
- Opposed Passive-Notice-vs-Stealth ties — now hit twice across two runs (both exactly 9-vs-9 and 7-vs-7-adjacent situations). Recommend an explicit tie-break rather than continuing to improvise one per session.
- Frenzy’s “drops defense completely” — does it include Parry? Now confirmed twice (original Run 2 pass and the corrected redo) to materially decide fight outcomes both times. Recommend just writing Parry into the rule text explicitly rather than leaving it as “illustrative examples.”
- Unaware-vs-Hazard-Roll player agency — the user’s own note: liked the brutality, wants to workshop a version that doesn’t leave a player as a spectator for a multi-round fight. Still open, by design (not something this simulation should resolve unilaterally).
Cross-scene Stress carry-over with no Breather opportunity (Sluice Vault → Frost-Cave)— Answered by the corrected Frost-Cave Troll redo: it’s not a pacing footnote, it’s a direct cause of an Incapacitation and a near-death. Recommend deciding whether that’s the intended difficulty curve for this module or whether a rest beat belongs between those two scenes.- New — the Stress-to-Wound exchange rate at Breaking has no written ratio. The corrected Troll redo had to borrow the Blood Price feat’s 2:1 rate by analogy and improvise a rounding rule for odd leftover points. Came up 5 times in one fight and decided an Incapacitation. Needs a real, written rate.
- New — paying a Miracle’s Locked Stress cost can trigger Breaking before its own Tithe roll resolves, meaning the roll should carry the Breaking penalty rather than whatever the caster’s pre-cast Stress level implied. Not currently written anywhere in Iron Core.
- New — does a Frenzied (“fights to death”) monster prioritize a free Coup de Grâce on a downed PC over fighting an active threat? Materially changes how dangerous being Incapacitated is for the rest of a fight. Deliberately left unresolved for GM judgment this session rather than settled unilaterally.
- New — does a mid-activation state change (e.g., failing an environmental Dodge check) retroactively apply to that same activation’s already-declared action? The corrected redo ruled yes (Troll’s Sweeping Uproot got re-rolled with Advantage after Frenzy triggered from the same activation’s failed flask check) — worth a one-line GM-guidance confirmation.
- New — Desperate Edge (single natural 6, exploding die) was never applied in any simulation this session, despite Winded explicitly being one of its two qualifying desperate states (the other is final Wound Slot). Caught after the fact, not during play. In the corrected Frost-Cave Troll redo alone, a raw dice review found roughly a dozen missed triggers — Perpetua’s and Ox’s defense rolls while Winded/Breaking, Ox’s Bleed-Out check while Incapacitated, and the Troll itself repeatedly once its own Stress hit 50%+ (Desperate Edge isn’t restricted to PCs, consistent with how Snake Eyes-in-Clash was ruled to apply to NPCs too). Several of the missed instances were single-margin Clashes where an exploding die could plausibly have flipped the result, including ones feeding into Ox’s Incapacitation. Run 1 and the original (pre-correction) Run 2 almost certainly have the same miss, but the raw dice from those runs weren’t preserved to audit. Logged as a finding, not re-run — the user has opted to hold this rather than trigger a third full re-simulation of the scene; a future re-run of any scene should apply Desperate Edge correctly from the start rather than patching historical results.