nemo-relay-debug-runtime-integration

# Debug Runtime Integration Use this skill when NeMo Relay is present in the application but something is not working. Start by proving which runtime layer is failing before changing configuration. ## First Checks - Can the binding or native artifact load? - Is there an active scope when the failing call runs? - Is the work happening on the expected scope stack? - Is the subscriber/exporter/plugin configuration actually active? - Did the app choose the right public API layer: managed execute vs manual lifecycle vs typed wrappers vs adaptive/plugins? ## Common Failure Classes - Python native extension missing - Go dynamic library not on the loader path - Node native addon not built or not loading - Execute call outside a scope - Missing events because registration never happened - Concurrency causing the wrong scope stack to be active - Adaptive component never initialized or config validation ignored ## Embedded Troubleshooting Matrix - **Rust build failure**: run the narrowest core build first, then expand to the affected binding or workspace command. - **Python import failure**: rebuild the virtual environment and native extension with `uv sync`, then run a small Python test or import check from the same environment as the application. - **Node.js addon failure**: reinstall and rebuild the native addon from the Node binding package before debugging application code. - **Go loader failure**: build the release FFI shared library and point both the linker an...