Evidence (adv_live1 + adv_live2, 2026-07-22): both live arc-duo runs terminated at beat 7 via the runner's 'DM went silent; stopping early' break — the final chat row is a FAILED DM beat (beat_failed:true, 'The tale falters — the Dungeon Master could not resolve this beat'). adv_live2's engine state at termination: combat ACTIVE, 3 living hostiles (Goblin Boss 21hp + 2 warriors), Aidan 5/28 — a real, correctly-unclosed fight cut off by the harness, not a DM discipline failure.
Reframe of the #1645 acceptance: the action-economy lever VERIFIED (action_economy_engaged flipped WARN→PASS; dice/combat_resolved PASS; real damage both ways). The closure WARNs in adv_live2 are CORRECT behavior (hostiles alive ⇒ end_combat would be wrong; the nudge rightly silent at no_hostile_turns=0). The remaining blocker to boss_dead/quest_completed is DM-BEAT RELIABILITY at depth ≥7.
Suspects (route via worldos-latency-forensics — SDK-instrumented measurement, not guesses): accumulated DM session context by beat 7 (each beat compounds transcripts ~120-270KB observed); a per-beat timeout in the runner's turn/turn_retry path classifying a slow beat as REAL failure; or a transient API class the retry classifier mislabels. The retry classifier's transient-vs-real call at run_adventure.sh:355 is in scope.
Acceptance for the fix: adv_live3 sustains ≥12 beats (or completes), zero beat_failed rows, with the per-beat latency series recorded.
Companions: #1645 (levers verified, remains open pending a full-arc completion), #1655, §9.1.
Evidence (adv_live1 + adv_live2, 2026-07-22): both live arc-duo runs terminated at beat 7 via the runner's 'DM went silent; stopping early' break — the final chat row is a FAILED DM beat (beat_failed:true, 'The tale falters — the Dungeon Master could not resolve this beat'). adv_live2's engine state at termination: combat ACTIVE, 3 living hostiles (Goblin Boss 21hp + 2 warriors), Aidan 5/28 — a real, correctly-unclosed fight cut off by the harness, not a DM discipline failure.
Reframe of the #1645 acceptance: the action-economy lever VERIFIED (action_economy_engaged flipped WARN→PASS; dice/combat_resolved PASS; real damage both ways). The closure WARNs in adv_live2 are CORRECT behavior (hostiles alive ⇒ end_combat would be wrong; the nudge rightly silent at no_hostile_turns=0). The remaining blocker to boss_dead/quest_completed is DM-BEAT RELIABILITY at depth ≥7.
Suspects (route via worldos-latency-forensics — SDK-instrumented measurement, not guesses): accumulated DM session context by beat 7 (each beat compounds transcripts ~120-270KB observed); a per-beat timeout in the runner's turn/turn_retry path classifying a slow beat as REAL failure; or a transient API class the retry classifier mislabels. The retry classifier's transient-vs-real call at run_adventure.sh:355 is in scope.
Acceptance for the fix: adv_live3 sustains ≥12 beats (or completes), zero beat_failed rows, with the per-beat latency series recorded.
Companions: #1645 (levers verified, remains open pending a full-arc completion), #1655, §9.1.