Pre-release 3.0.1 M2 Runtime Triage

Prompt file imported from akspa0/parp-tools (.codex/prompts/pre-release-3-0-1-m2-runtime-triage.md). Copyright stays with the author.

Use this prompt after code changes when a pre-release 3.0.1 model still fails, partially loads, or renders with bad transparency.

Read First

1. gillijimproject_refactor/documentation/pre-release-3.0.1-m2-wow-exe-guide.md
2. .codex/prompts/pre-release-m2-rendering-recovery.md
3. gillijimproject_refactor/src/MdxViewer/memory-bank/activeContext.md

Goal

Decide which track the current runtime failure belongs to:

1. Track A: pre-release 3.0.1 parser or layout compatibility
2. Track B: pre-release 3.0.1 material, effect, or shader-era feature support that Warcraft.NET does not fully model
3. Track C: shared texture, material, blend, or shader parity

Required Inspection Files

1. gillijimproject_refactor/src/MdxViewer/ViewerApp.cs
2. gillijimproject_refactor/src/MdxViewer/Rendering/WarcraftNetM2Adapter.cs
3. gillijimproject_refactor/src/MdxViewer/Terrain/WorldAssetManager.cs
4. gillijimproject_refactor/src/MdxViewer/Rendering/WmoRenderer.cs
5. gillijimproject_refactor/src/MdxViewer/Rendering/ModelRenderer.cs

Required Triage Steps

1. Identify the exact failure stage:
   • path resolution
   • container gate
   • typed validator
   • skin/submesh mapping
   • converter fallback
   • material/effect metadata extraction
   • texture lookup
   • shader or effect feature mapping
   • transparency routing
   • shader behavior
2. Classify the asset itself:
   • plain opaque/static
   • cutout/translucent
   • effect-heavy or shader-driven
3. State whether the model reached renderable geometry.
4. State whether the remaining issue reproduces on classic MDX, M2-family assets, or both.
5. State whether the evidence points to missing extracted data, missing renderer behavior, or both.
6. Keep build-only evidence separate from runtime evidence.

Deliverables

Return all items:

1. Exact failure stage
2. Whether the remaining issue is Track A, Track B, Track C, or a combination
3. Whether Warcraft.NET abstraction limits are part of the failure
4. Concrete next code slice to change
5. Validation status and missing runtime evidence
6. Any guide or memory-bank updates required

First Output

Start with:

1. the observed runtime symptom
2. whether the asset looks plain or effect-heavy
3. the most likely failure stage
4. the first file you will inspect