KB: issue-3 pickup trail -- bvx9_mtl scorch quad + crunch-vs-full explosion

Human-verified: wreck swap works live; small ram explosion visible.
Remaining detail recorded for the next session.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

context/rendering.md

@@ -267,7 +267,12 @@ DPLStaticChildRenderable/DCSInstanceRenderable at TOP level — those read the b
 MECHMOVR truck → ram death → MECHMD wreck debris scattered at the truck's spot. ⚠ STILL OPEN
 (#3): (a) the wreck's scorch base quad draws as an opaque BLACK rectangle (MECHMD's own op —
 material/ramp resolve); (b) the death Explosion (psfx 1008 ddam5) not visually confirmed;
-(c) the authored BurningState fire visual unreconstructed. LESSON: `[cultvis]` log lines verify
+(c) the authored BurningState fire visual unreconstructed. PICKUP TRAIL for (a): the black
+square is MECHMD.bgf patch 0 — a 4-vtx NO-NORMAL quad (VTX_XYZ_UV), material `basev:bvx9_mtl`
+(BASEV.BMF; scratchpad/dump_bmf.py truncates before its record) — the no-normal ramp/material
+resolve path renders it void-black instead of the authored scorch. For (b): the ram fires the
+CRUNCH explosion res 31 (small, human-seen); res 32 is the icon's non-crunch explosion —
+check which the weapon-kill path should fire + psfx scale vs period footage. LESSON: `[cultvis]` log lines verify
 the STATE MACHINE, not pixels — only a screen check (BT_SHOT / human) verifies rendering.
 Diags: `BT_CULT_LOG` (census/damage/death + `[cultvis]` + `[cultobj]` per-object file/type/op
 flags). MP: replicants transition via `ReadUpdateRecord` → same SetState watcher path (untested