healer-man/docs/ROM_NATIVE_ROUTE_PLAYTEST_2026-10-04.md

# RoM Native Party Campaign Route Playtest — 2026-10-04

> **Current QA policy (2026-10-05):** Routine live tests use Stormwind Stockade: Cellblock Rush (`bite-sized-stormwind-stockade`); record the boss selected from the run ID. Full-source Stockade campaigns require explicit route selection. The Wailing captures and commands in this dated report remain historical; follow [the current test policy](TEST_DUNGEON_POLICY.md) and root `AGENTS.md`. A new Wailing reproduction needs an explicit owner request.

## Scope and build

Tested bounded entrance-to-encounter segments in Barren Caves and Wailing Caverns using the ordinary campaign picker. Each run used a UI-created level-30 RoM Priest / Knight healer and four active RoM NPC companions. Both dungeons entered in healer role with `gameMode=dungeon`, `gmTestMode=false`, and no Boss Testing state. Only initial profile level and secondary class were prepared for the isolated test profile. Dungeon entry, WASD movement, Tab targeting, party commands, ability keys, and ally selection used the game UI and normal inputs. Combat health, mana, damage, positions, cooldowns, enemy health, and targets were not changed by the harness.

The confirmed final production build used `index-CAMDJqEC.js`, `combatStore-t7bO4yKt.js`, `GameRuntime-otPnJCWI.js`, `PartyFrames-BsBsesPR.js`, and `index-499eecpe.css`.

## Roster Continue hit test

On the final build, the actual Continue button was clickable normally at both tested sizes. The 1440×900 layout and the 390×844 compact layout had no overlap with the floating toggle, and `elementFromPoint` at the button center hit Continue in each. The run recorded `forceClickUsed=false`.

- [Desktop Priest/Knight roster](../playtest-artifacts/native-routes/final-20261004-052623521/roster-priest-knight-level-30.png)
- [Compact Priest/Knight roster](../playtest-artifacts/native-routes/final-20261004-052623521/roster-compact-priest-knight-level-30.png)
- [Hit-test measurements and full run result](../playtest-artifacts/native-routes/final-20261004-052623521/results.json)

## Route results

| Campaign segment | Input and endpoint | Support and combat outcome |
| --- | --- | --- |
| Barren Caves, 90-second segment | 41 WASD movement steps; 68.13 m summed keyboard displacement and 69.34 m game distance; ended at “Uncharted Barren Caves.” | 15 effective player heals (6,154.63 total) and 7 effective player damage events (549 total); no party deaths. The level-30 profile naturally reached level 31. The endpoint view is partly blocked by a cave pillar, so this run demonstrates bounded movement and combat, not camera visibility or full navigation. |
| Wailing Caverns, fresh level-30 profile, 90-second segment | F1 Attack then F2 Defend; 15 WASD movement steps; 23.12 m summed keyboard displacement and 23.76 m game distance; ended at “The Winding Chasm - Entrance.” | 11 effective player heals (6,831.49 total), zero effective player damage events, and no party deaths. Three distinct entrance mob records were observed dead across snapshots: Deviate Guardian, Deviate Ravager, and Druid of the Fang. This does not claim a full route or total dungeon kill count. |

The Wailing run selected the longest-range bound hostile ability, Rising Tide (21.7 m), and used Urgent Heal (25 m). The first Wailing diagnostic had kept the party and healer too far apart and lost Rorik; that trace is preserved at `final-20261004-051737171` as a harness-policy diagnostic. The final run sampled live NPC positions, waited for healing casts to resolve, and issued F2 Defend after the initial F1 pull. Rorik survived this bounded segment, but the run produced no effective player damage, so it provides no player-DPS coverage.

The observed school list is from the combined combat event stream, including player and NPC activity; it does not establish that each enemy used every listed school. `killedMobNames` describes dead mobs still present in the endpoint snapshot. Wailing's three names above are the distinct dead records sampled during the segment, not a complete kill ledger.

## Evidence

**Barren Caves** — completed route record and screenshots:

- [Route JSON](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-route.json)
- [Campaign picker](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-campaign-picker.png)
- [Entrance](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-entrance.png)
- [Keyboard traversal](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-keyboard-traversal.png)
- [Encounter midpoint](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-encounter-midpoint.png)
- [Segment endpoint](../playtest-artifacts/native-routes/final-20261004-051413627/barren-caves-segment-end.png)

The combined Barren/Wailing attempt has a follow-on `failure.json`: after Barren naturally advanced the profile to level 31, a harness assertion expected level 30 before starting the second route. The Barren route JSON and its screenshots are complete and are reported independently. Wailing was then run in a fresh level-30 profile.

**Wailing Caverns** — independent final route record and screenshots:

- [Run summary](../playtest-artifacts/native-routes/final-20261004-052623521/results.json)
- [Route JSON and detailed movement/heal records](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-route.json)
- [Campaign picker](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-campaign-picker.png)
- [Entrance](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-entrance.png)
- [Keyboard traversal](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-keyboard-traversal.png)
- [Encounter midpoint](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-encounter-midpoint.png)
- [Segment endpoint](../playtest-artifacts/native-routes/final-20261004-052623521/wailing-caverns-segment-end.png)

Both route runs reported zero browser page exceptions. Each recorded one console-level 404 for the local `/favicon.ico` request. The Wailing run also records normal keyboard events, party positions, health and mana at entry and endpoint, cast outcomes, and sampled enemy deaths.

## Harness

The current `node scripts/playtest-native-routes.cjs --route-seconds=90` default runs an independent UI-created profile and one bounded **Stormwind Stockade: Cellblock Rush** segment; its boss is selected from the run ID and should be recorded. An explicitly requested full-source Stockade route uses `--route=stormwind-stockade`; Barren uses `--route=barren-caves`. Historical Wailing reproduction requires the owner's explicit request and `--historical-wailing --route=wailing-caverns`; it is not a default. The captures above used the older two-route harness. Run and review each authorized route independently to control its starting profile at level 30.