Release Healer Man 0.1.22

dungeon-pipeline/README.md

@@ -92,8 +92,10 @@ whose preserved source has no recoverable combat ability is explicitly marked
 
 Stock AzerothCore population is used for the standard dungeons. The three
 Ascension-specific instances—Tinkertech Showdown, Frozen Reach, and Forgotten
-Mine—keep their client encounter identities and use an explicit procedural
-trash-population fallback. Non-Epoch recipes keep explicit procedural actor
+Mine—keep their recovered client identities, spell/summon evidence where
+available, and explicit source-backed or HealerMan-authored runtime adaptations.
+Their remaining procedural population is never labeled authoritative.
+Non-Epoch recipes keep explicit procedural actor
 bodies until reviewed display exports are available. Epoch actors use packaged
 client GLBs with their complete native animation libraries; only event-only
 controllers without a creature display fall back.
@@ -160,10 +162,13 @@ The audit verifies the complete 54-dungeon catalog, authoritative/fallback
 classification, every native environment and creature URL, file sizes,
 checksums, animation presence, and compiled entry-to-model bindings. The
 2026-07-26 batch packaged 50 native imports; together with the Wailing Caverns
-golden fixture, 51/54 dungeons are authoritative. Tinkertech Showdown, Frozen
-Reach, and Forgotten Mine remain documented fallbacks because available local
-sources contain their maps and encounter identities but no authoritative
-Ascension creature templates, display mappings, or spawn rows.
+golden fixture, 51/54 dungeons have authoritative WoW population packages.
+Tinkertech Showdown, Frozen Reach, and Forgotten Mine now have playable,
+provenance-labeled runtime adaptations backed by
+`ascension/ASCENSION_CUSTOM_DUNGEON_RECOVERY.json`. They remain outside the
+authoritative package count because the recovered client evidence does not
+include complete Ascension creature templates, display mappings, spawn/object
+coordinates, or server-side cadence.
 
 1. `npm run dungeon:discover -- <slug>` writes deterministic client/server
    snapshots, a provenance lock, review-required overrides, and—when server
@@ -224,9 +229,14 @@ The default pass recompiles the 54-dungeon campaign, verifies all packaged
 environment and creature assets, audits every mob and boss attack/mechanic,
 opens every unique native creature GLB to verify idle, movement, attack, wound,
 and death clips, proves the procedural animation path for model-less actors,
-and runs the actual runtime-registry coverage test. It writes deterministic
-JSON and Markdown reports to WOW_DUNGEON_CONTENT_REPORT.json and
-WOW_DUNGEON_CONTENT_REPORT.md.
+runs the actual runtime-registry coverage test, and audits instance-level
+functionality. It writes deterministic JSON and Markdown reports to
+WOW_DUNGEON_CONTENT_REPORT.json, WOW_DUNGEON_CONTENT_REPORT.md,
+WOW_DUNGEON_FUNCTIONALITY_REPORT.json, and
+WOW_DUNGEON_FUNCTIONALITY_REPORT.md. Catalog compilation also writes
+WOW_GAMEOBJECT_ASSET_MANIFEST.json, which deduplicates the source-backed object
+spawns by client model path, preserves per-dungeon/display usage, assigns the
+planned shipping GLB URL, and lists unresolved display models and bounds.
 
 Useful batch options:
 
@@ -239,11 +249,40 @@ Useful batch options:
     # Re-run green packages, then build the app after validation.
     npm run dungeon:wow:all -- --refresh --force --build
 
-    # Only re-run combat, mechanic, and animation coverage against current output.
+    # Re-run combat, animation, and instance-functionality audits against current output.
     npm run dungeon:wow:all -- --audit-only
 
-Kresh is intentionally recorded as a source-faithful melee-only boss: entry
-3653 has no spell or SmartAI row in the pinned AzerothCore snapshot. Trial of
-the Champion is likewise documented as a boss-arena population rather than a
-trash route. These exceptions are asserted by exact dungeon/entity IDs; any
-new basic-only boss or mob-less dungeon fails the batch.
+The functionality report is the production-fidelity gate. It separately checks
+typed world-object contracts, source instance scripts, encounter orchestration,
+required interactions, traversal evidence, resets, checkpoints, and completion
+playtests. A green asset or combat audit does not imply that doors, escorts,
+waves, vehicles, keys, chests, or scripted instance progression are implemented.
+The report fails closed and lists concrete edit targets for every remaining
+dungeon gap.
+
+The 2026-09-08 implementation sweep completed an instance-level source review
+for all 54 campaign dungeons. Fifty-one now have runtime-wired reviewed
+orchestration in addition to fleet boss/checkpoint/completion declarations; the
+three stock instance scripts that are genuinely empty are pinned and recorded
+as source-exact no-ops. This means there is no remaining unreviewed instance
+script, not that every source feature is already exact or live-traversal validated. Per-dungeon adaptations,
+missing primitives, native-object export work, and live traversal evidence stay
+open in `WOW_DUNGEON_FUNCTIONALITY_REPORT.md`.
+
+Source-backed object records stay hidden, non-blocking, and non-interactive
+until their manifest asset has been exported and the corresponding instance
+script transition has been reviewed. This lets the typed data ship through the
+runtime contract without leaking placeholder geometry or turning an incomplete
+door/transport port into a dungeon soft lock.
+
+Kresh, the Deviate Faerie Dragon, Grubbis, Spirestone Battle Lord, Spirestone
+Butcher, and Crystal Fang are intentionally recorded as source-faithful
+melee-only bosses. Kresh entry 3653 and the Deviate Faerie Dragon entry 5912
+have no spell or SmartAI row in the pinned AzerothCore snapshot; the latter is
+also despawned by the Wailing Caverns initialization event. Grubbis entry 7361
+has only aggro dialogue and death-completion rows, with no combat spell cast.
+The three Blackrock Spire entries are 15% rare spawns whose database rows
+contain no active combat cast; Crystal Fang's exact on-death Spire Spiderling
+summon is implemented by the reviewed instance adapter. One shared exception
+table supplies the runtime test and composed-content audit; stale, duplicate,
+or newly introduced basic-only boss keys fail the batch.