Release Healer Man 0.1.59

PLAYTEST_NOTES.md

@@ -4033,3 +4033,57 @@ Vite's existing large-chunk advisory remains informational.
   at z=370, 390, 410, 430, 445, and 460 also stood on collision in the live
   client; the source guard points and boss position have collision and
   navigation surfaces.
+
+## Paused browser memory (2026-09-26)
+
+- A fresh offline Wailing Caverns Bite-Sized run in headless Edge entered the
+  dungeon, opened the pause menu, and held it for 60 seconds. The paused scene
+  used R3F's `demand` frame loop and reported no browser page errors. Before
+  the classic talent lookup change, forced-GC JavaScript heap remained at
+  266 MiB across 0, 15, 30, and 60 seconds; DOM node count also stayed flat.
+- `src/game/wow335AbilityCatalog.ts` now validates classic talent IDs through
+  the already loaded compact runtime talent catalog. The built classic ability
+  chunk fell from 41.4 MiB to 2.1 MiB, because it no longer includes the
+  36.6 MiB CoA source catalog. The same paused browser run measured 155, 155,
+  155, and 156 MiB after forced GC at 0, 15, 30, and 60 seconds. The paired
+  screenshots and samples are in `playtest-artifacts/pause-memory/`.
+- The one-minute sample did not show a growing JavaScript heap. It does not
+  measure GPU allocations or rule out growth in a different dungeon or over
+  a longer idle period.
+
+## Character-specific catalog loading (2026-09-26)
+
+- The production build now imports `src/game/romBaseStatGrowth.generated.json`
+  (4.5 KB) for shared stat calculations. The full 1.7 MB
+  `romPlayerCatalog.generated.json` remains in the RoM ability chunk and is
+  requested only when a RoM class needs its abilities.
+- `src/game/talentRuntimeCatalog.ts` loads its generated WoW/CoA talent data
+  after a non-RoM class requests combat catalogs. A fresh RoM Rogue main-menu
+  session fetched `romAbilityCatalog-*.js` without fetching either the
+  `wow335AbilityCatalog-*.js` or the talent-data chunk. A fresh WoW Priest
+  fetched the classic ability and talent-data chunks without fetching the
+  RoM ability chunk. Both sessions had no browser page errors.
+- The RoM Rogue roster and Wailing Caverns dungeon smoke test passed with the
+  WoW/CoA talent data absent from the initial RoM page load. Browser request
+  results and menu screenshots are in `playtest-artifacts/catalog-loading/`;
+  dungeon screenshots are in `artifacts/playtest/rom-five/`.
+
+## Browser memory reset at shell boundaries (2026-09-26)
+
+- Browser ES modules cannot be unloaded individually from an active page.
+  Changing to a different character now reloads the page with a one-use
+  `sessionStorage` handoff to restore the selected character and destination.
+  Leaving a gameplay mode for the roster or main menu also reloads after the
+  run's normal save path. A live online group activity suppresses this reset
+  to avoid re-entering the same activity on reconnect.
+- The main-menu catalog gate no longer reloads the full gameplay runtime or
+  retains talent art up front; it preloads those resources when gameplay starts.
+- In a production Edge playtest, switching from a WoW Priest to a RoM Rogue
+  produced one reload and returned to the RoM main menu. The WoW talent editor
+  opened on demand before that switch. The new RoM page loaded
+  `romAbilityCatalog-*.js` without a WoW ability or `GameRuntime` chunk.
+  Leaving a RoM Wailing Caverns run produced a second reload and returned to
+  the same character's main menu without a `GameRuntime` chunk. Switching to
+  another RoM character also reloaded. The one-use handoffs were consumed,
+  and the page reported no errors. Results and screenshots are in
+  `playtest-artifacts/memory-reset/`.