What problem does it solve? Operators of the SparkEngine C++ game engine need verified, repo-grounded instructions for launching engine binaries, bounding runs for smoke tests, producing distributable packages, and reading the release pipeline's evidence without conflating "built" with "published". ## Core Features & Use Cases - Launch runbook: Documents every runtime flag (-headless, -game, -test-frames, -exec), the module selection order, and copy-paste launch commands for windowed, headless dedicated server, and editor modes. - Smoke testing: Defines bounded-run recipes that pair exit codes with log evidence under the per-user %LOCALAPPDATA%/SparkEngine/Logs directory. - Packaging and release: Covers CMake install + CPack packaging (ZIP/NSIS/WIX/TGZ), the real status of the two in-engine GamePackagers, and the release.yml workflow's triggers, gates, and artifact evidence via gh commands. - Use Case: A CI engineer sees "CI is green but the nightly release failed" and uses the documented evidence commands (gh run view, gh release view nightly) plus the local CPack/PackageSmoke reproduction recipes to pinpoint the release-only gate that broke. ## Quick Start Ask the assistant to launch the SparkEngine headless dedicated server with the SparkGameMMOFPS module bounded to 60 test frames and verify the exit code and log output.