Don't stub numpy in sys.modules in a shared pytest session
A maintainer rejected a test that briefly swapped a stub numpy (and other modules) into sys.modules to import a driver file in isolation. Their node test session pins numpy with a guard (a _sys_modules_guard module), because any module first imported while the stub sits in sys.modules keeps a reference to the fake for the rest of the session, which causes confusing failures in unrelated tests. Before writing a custom importlib loader with scoped stubs, check how sibling tests import the code. Here the test environment already provided the engine imports, so a plain 'from nodes.<pkg>.<module> import Store' replaced about 50 lines of loader machinery. Use stubs only for dependencies the test env truly lacks, and never for widely shared libraries like numpy.