Integrate battles with the overworld UI and validate browser flows

- Drive wild battles through the real UI in Chromium and WebKit using a
  test-only encounter fixture: victory with level-up, escape, whiteout,
  mid-battle backup restore and unsupported-effect rollback.
- Add keyboard and on-screen D-pad navigation for battle menus.
- Accept pending stat experience in saves (awarded without CalcMonStats).
- Commit whiteout healing, money loss and destination callbacks together;
  aborted scripts restore state and map.
- Give long notices their own status-bar row on narrow screens.

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

docs/ARCHITECTURE.md

@@ -48,4 +48,4 @@ Asset caches and the ROM reader remain in memory for lazy extraction. Neither RO
 
 The native viewport follows its available CSS dimensions and draws additional world tiles at a bounded pixel resolution. Beyond a map's edge it draws the connected map with the current tileset, as the original connection strips do, and the border block elsewhere. Resizing also redraws paused sessions. The local minimap caches terrain from the loaded map and updates its marker from the same world position used by the player; the Map tab shares that view. It is a current-area map, not a full region atlas. Leaving Game pauses the session and releases held input; returning requires explicit play. The reference player retains its own fixed-screen styling.
 
-`game/battle` now holds the native battle core and ROM-backed battle tables. Its unit and damage/type reference tests do not yet establish the full overworld-to-battle browser flow. Introduce future modules with working features: `game/audio`, then `features/link` and `features/walking`. Party and bag models live in `game/party`; scripts change them only on their draft state. Rules must not import UI/browser modules. Transports and step providers must not write directly into world state.
+`game/battle` now holds the native battle core and ROM-backed battle tables. Browser tests cover the overworld-to-battle flow using a test-only encounter fixture; no production map has encounters enabled yet. Introduce future modules with working features: `game/audio`, then `features/link` and `features/walking`. Party and bag models live in `game/party`; scripts change them only on their draft state. Rules must not import UI/browser modules. Transports and step providers must not write directly into world state.

docs/PLAN.md

@@ -49,7 +49,7 @@ The emulator-backed prototype is now at `/reference.html`. The default applicati
 
 ## In progress: native battles
 
-The battle core, ROM tables, encounter hooks, battle UI and whiteout hooks are present. Unit tests cover wins, escape, loss, experience and move learning; reference tests compare damage and type effectiveness. Full browser battle flows, capture, Route 29 scripts and the opening quest remain unverified or unfinished.
+The battle core, ROM tables, encounter hooks, battle UI and whiteout hooks are present. Unit tests cover wins, escape, loss, experience and move learning; reference tests compare damage and type effectiveness. Browser tests drive a test-only wild encounter through the real UI: victory with level-up and move learning, escape, whiteout, keyboard and on-screen D-pad menu navigation, mid-battle backup restore, and rollback of unsupported effects. Capture, switching, items in battle, Route 29 scripts and the opening quest remain unfinished.
 
 This is still not a complete new game. Playable battles, party/bag/Pokégear menus, story progression beyond the lab, NPC roaming, decorations, animated terrain, surfing, entering routes and audio remain unfinished. Save slots, a Johto/Kanto atlas, Pokédex records, online Link, friends and real-world steps come later.
 

docs/SESSION_HANDOFF.md

@@ -100,3 +100,33 @@ opening scenes. Audit Route 29 callbacks, scripts and unsupported destinations
 before enabling it. Then test wild encounters and battle controls through the
 browser, including win, escape, loss and save/reload, and reconcile the roadmap
 with the verified behavior.
+
+## Battle integration increment: 2026-09-23 (resumed from Codex)
+
+Codex committed and pushed `c08d250`, then stopped mid-increment with the
+keyboard/D-pad battle test failing. Claude Code completed it:
+
+- Browser battle flows run through the real UI via `tests/battle-fixture.ts`
+  (encounter selection only; production maps stay gated): win with level-up and
+  Smokescreen, escape, whiteout, keyboard/D-pad menus, mid-battle backup restore
+  and unsupported-effect rollback. `tests/battle-world.test.ts` covers the same
+  at world level, plus pending stat experience and whiteout callback rollback.
+- Saves accept stored stats between the no-stat-exp and full-stat-exp values,
+  since `GiveExperiencePoints` awards stat experience without `CalcMonStats`.
+- A script warp (e.g. whiteout) validates its destination and commits healing,
+  money loss and destination callbacks together; aborts restore state and map.
+- Keyboard and on-screen D-pad navigate battle menus (`battle-selected`); A
+  continues messages, B leaves the move list.
+- Fixed a phone-width layout bug: a long notice sat in the Play button's auto
+  grid column and crushed the status text, pushing the game panel off-screen.
+  Below 720px the notice now has its own row.
+- Test fixes: the navigation test now presses A through the intro message, and
+  uses a real pointer click on the D-pad (synthetic pointer events cannot be
+  captured).
+
+Final checks: 82 unit tests with the local ROM (55 passed, 27 skipped without
+it); 36 Chromium/WebKit browser tests; native and reference builds; release,
+vendor and reference checks; `git diff --check`. Not committed.
+
+Next: Route 29 (`24:3`) scripts, catching tutorial and items before enabling it;
+then capture, switching and PACK in battle.