Release Healer Man 0.1.37

PLAYTEST_NOTES.md

@@ -2439,3 +2439,122 @@ Vite's existing large-chunk advisory remains informational.
   tests remained skipped. Final production TypeScript/Vite compilation, texture
   and performance audits, static compression, and bundle verification passed.
   Existing chunk-size advisories remain. No hosted release was published.
+
+## 2026-09-12 - HoTs and regeneration cannot heal corpses
+
+- Reproduced the reported death-with-HoT state through lethal damage followed
+  by overdue Rejuvenation ticks; the original implementation restored health
+  while retaining the death animation. Separate failures confirmed passive
+  spirit/equipment regeneration, ground healing, triggered healing procs, and
+  a lingering damage tick's level-up refill could also restore corpse health.
+- Kept the fix in combat simulation rather than scene movement. Ordinary
+  player healing in mutable combat work now uses a shared living-target guard;
+  passive regeneration preserves zero health. Timed effects validate their
+  target before ticks and procs, discard HoTs on dead targets even before the
+  next tick, and retain HoTs on living allies when their caster dies. Newly
+  applied actor HoTs also reject dead targets. Ground healing skips corpses
+  while continuing to heal living teammates. Experience may still be awarded
+  after death, but its level-up refill no longer implicitly resurrects.
+- Explicit player and actor-based party resurrection remain available and
+  synchronize restored actor health/alive state. Party resurrection also
+  clears the death animation using the existing ability-cancel event. Normal
+  checkpoint respawn still restores health and clears lingering effects.
+  The existing player movement gate remains unchanged and blocks zero health.
+- Fifteen new regressions cover the original self-HoT failure, actual Priest
+  Renew, overdue/future ticks, explicit companion-to-player HoTs and their
+  healing logs, dead allies, regeneration, ground healing, proc healing,
+  post-death level rewards, living-target healing, resurrection, and respawn.
+  The final focused combat/death/support checks passed 101 tests; the full
+  suite passed all 230 files and 1,459 tests with six existing skips.
+- No live corpse-movement replay or physical Android check was performed in
+  this pass. Evidence is combat-state regression coverage, not a new visual
+  claim. Character rendering, camera/input, dungeon assets, lighting, and
+  navigation policy were not modified. No hosted release was published.
+
+## 2026-09-12 - Selectable resurrection checkpoints and fallen NPC recovery
+
+- Normal dungeons now offer the entrance plus every defeated boss as named
+  resurrection destinations. Choices use authored boss locations, not corpse
+  coordinates, and unlock from actual defeated actors or durable encounter
+  objective completion. Alive/script-despawned bosses and invalid destination
+  IDs cannot grant a checkpoint. Boss-wipe resets retain completed checkpoints;
+  a fresh dungeon run clears its progress.
+- The player defeat prompt includes a destination chooser. Respawning at the
+  entrance or a cleared boss retains defeated enemies and run progress while
+  resetting the current pull and restoring the party through the existing
+  respawn lifecycle. Legacy callers without a choice retain saved-spawn behavior.
+- A contextual `Rez dead members` button and matching destination chooser appear
+  below the party frames whenever an NPC teammate is dead. Only fallen NPCs are
+  revived, at full health, into their formation slots at the selected checkpoint.
+  Living NPCs, the player's health/location, current enemies, and party orders
+  are not reset. Lingering timed effects on revived NPCs are removed without
+  removing living allies' HoTs. Manastorm charges and remote human resurrection
+  behavior are unchanged; non-authority online clients cannot mutate NPC revival.
+- Living, engaged bosses disable the NPC chooser/button with an explanation;
+  the same restriction is checked again when the action executes. Trash combat
+  does not block it. Individual return tasks use approved navigation toward the
+  player's current location, including while the party is on Stop, then resume
+  the current order. Returning members do not cast/taunt from the checkpoint or
+  skew the engaged squad's target-selection center. Existing validated stuck
+  recovery remains available. Recall, death, actor unmount, and run reset cancel
+  pending return tasks. Scene relocation clears the corpse animation explicitly.
+- Live localhost Stockades screenshots at 1280x720 showed the panel with a dead
+  Morvane tank, an enabled entrance chooser/button during trash combat, and the
+  tank restored to 1707 health at the entrance after clicking while Stop remained
+  selected. The button disappeared when no NPC was dead; living Thorne continued
+  taking damage rather than receiving a party-wide refill. At 384x844 both native
+  chooser and button remained within the viewport, about 176px wide and 44px high.
+  The narrow screenshot capture was backend-scaled, so DOM bounds supplemented
+  the visual check. Normal viewport sizing was restored and the temporary tab
+  and development server were closed.
+- Twenty-nine new regressions cover checkpoint unlocking/retention, invalid and
+  locked choices, player checkpoint respawn, boss/trash restrictions, selective
+  NPC revival/effect cleanup, authority/Manastorm isolation, Stop/rejoin behavior,
+  wall-aware return navigation, registry lifecycle, and UI visibility/placement.
+  The shipping Stockades navigation/collision test also simulates all four NPC
+  formation slots walking from the entrance and every boss checkpoint back to
+  the entrance through approved corridors, without requiring stuck recovery.
+  Final Vitest validation passed all 234 files and 1,488 tests, with six existing
+  skips. No live boss-kill destination-selection, distant-player return replay,
+  multiplayer session, or physical Android check is claimed in this pass.
+- Browser logs contained no errors; Rapier initialization and KTX2-loader warnings
+  occurred during development hot reloads. Character assets, camera/input,
+  dungeon geometry, and lighting were not edited. Final production TypeScript/Vite
+  compilation, static compression, and release-bundle verification passed; texture
+  and environment-performance audits also passed during prebuild. Existing build
+  chunk advisories remain. No hosted release was published.
+
+## Optional DPS meter — September 12, 2026
+
+- Added a compact party DPS meter with current/last-fight damage, class-colored
+  rankings, and a shared fight timer. It consumes the lossless combat event
+  stream and counts effective damage, including pets/summons under their owner.
+  Completed fights remain visible until the next pull; encounter resets clear
+  the meter. Hiding it does not stop recording. Local menu/background pauses
+  do not dilute DPS.
+- Automatic placement uses the PC lower-left corner and the Thor companion
+  display. The UI editor supports visibility, dragging/keyboard nudges, width,
+  and screen selection. These settings participate in saved layouts, all six
+  template slots, and export/import, including migration of older UI files.
+  Dedicated companion snapshots carry meter data and draft placement; lower
+  display movement commands update the authoritative editor draft.
+- Live localhost Stockades checks at 1280x720 showed increasing party damage
+  and readable bars in the PC lower-left corner. Resizing from 230 to 240 pixels
+  worked; dragging moved the handle from approximately (9, 509) to (269, 400).
+  Saving visibility off hid the meter, and reopening the editor retained that
+  setting while damage continued accumulating. Default position/width and
+  visibility were restored after this check.
+- In Thor preview, the meter appeared only inside the 620x540 companion surface.
+  Populated bars remained clear of the party strip, vital controls, and action
+  bar. With the main editor open, dragging on the bottom screen moved its handle
+  from approximately (526, 322) to (661, 369) within companion bounds. Those
+  preview movement edits were canceled. Screenshots are saved in
+  `artifacts/dps-meter/pc-default.png`, `thor-default.png`, and
+  `thor-editor-moved.png`. Full-page capture scaled incorrectly in the browser
+  backend, so the Thor screenshots use the scrolled normal viewport.
+- All 47 targeted tests passed across seven files, including damage accounting,
+  ownership, reset/pause behavior, UI migration/persistence, and dedicated
+  companion publication/unsubscription. The production build and release
+  checks passed. Browser error logs were empty. Physical Thor hardware and a
+  multiplayer session were not exercised; the new per-party totals consume
+  this client's combat stream. No hosted release was published.