handoff: add the M1.5 dungeon-demo exit gate to the next-session work order

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/research/2026-06-12-night-session-handoff-108-residual-next.md

@@ -77,7 +77,15 @@ WORK ORDER:
    outdoor/terrain. Punch/seal are exonerated — do NOT touch them.
 2. Then #127 (admission churn; PortalBounds pre-gate suspect), #116
    (slide-response, oracle-first cdb), #125 sticky-drop debt.
-Closing this list ≈ the M1.5 → M2 boundary (M2 = kill a drudge).
+3. When the ledger clears: run the M1.5 DUNGEON DEMO as the milestone
+   exit gate (milestones doc: enter any dungeon via portal, 3-5 rooms,
+   walls block / stairs work / lighting correct / transitions smooth).
+   The old blocker #95 died with the Option A rewrite (the ACME BFS it
+   lived in was deleted in T4); the portal entry flow is field-tested
+   (the 2026-06-12 accidental teleport). Dungeon-specific findings
+   (likely A7 lighting items) get fixed inside M1.5; a clean demo lands
+   M1.5 -> update the milestones doc + CLAUDE.md and start M2 (kill a
+   drudge; first port target per the research memos: CombatMath).
 
 The user's reports are AXIOMS. Visual gates are the acceptance tests.
 Suites green per commit: App 261+1skip / Core 1439+2skip / UI 420 /