nx_enginelab_analysis.nx

nx_enginelab_analysis.nx -- EL2 replay, EL4 shader binding, EL5 stack sampling, EL6 call tree. WHY A FOURTH MODULE AND NOT MORE OF THE SPINE. Two lanes built the same rung inside one hour today and the collision was caught by the LINKER rather than by either lane looking first. The cheap structural answer is that a lane writes in files it owns and declares what it is taking BEFORE it writes: these four rungs are declared to the sibling lane, and event kinds 9 and 10 are claimed explicitly, because a silently reused KIND value is worse than a duplicate name -- the linker cannot catch it, and every analyzer would read the record as a valid one of the wrong type. EVERYTHING HERE IS PURE BUFFER. No path, no descriptor, no syscall beyond allocation. The spine stays adoptable by a wasm world and so does this. license_tier: ORIGINAL No hardware writes (Rule 26).