sparkengine-modules-sdk-abi-and-hot-reload

Rejection before OS load means the mandatory .sparkabi sidecar is missing, malformed, incompatible, or its SHA-256 does not match the DLL binary. Rebuild the module through spark_add_game_module so the sidecar is regenerated alongside the binary.

Dead module console commands on Windows indicate the SparkModuleInjectConsole export is missing, leaving registrations in a DLL-private console instance. Include Spark/ModuleDllMain.h in exactly one .cpp and verify the export exists in the built DLL.

The .sparkabi sidecar is a build-generated key=value file with 12 fields including SDK version, compiler ABI, and binary_sha256. ModuleManager validates it before LoadLibrary, so a module without one is invisible to discovery and refused before any of its code runs.

The wired ModuleHotReloadManager stages a replacement via shadow copy and only commits after successful initialization, preserving the old instance on failure. However, replacement OnLoad runs before old OnUnload, so modules with process-global registrations must handle that overlap.

SparkEngine enforces a single-game-module policy: exactly one ModuleKind::Game module may load per process, and a second one is hard-refused. Libraries and extensions must declare ModuleKind::Addon in their ModuleInfo to coexist.

Do not use it for shader hot reload, ECS phase ordering, CMake toolchain setup, or general crash triage unrelated to the module boundary. Those belong to the sibling rendering, ECS lifecycle, build/CI, and debugging-playbook skills respectively.