Development, validation, packaging, and releases run locally. Do not add
.github/workflows or another hosted CI configuration.
The root validation script is the stable entry point:
./scripts/check.ps1As components become executable, that script will call their own checks while preserving a single local command for contributors.
Do not store model-provider or geographic-data credentials in the repository. The companion will call named capabilities through the private AI layer. OpenAI can be the initial backend while the game-facing contracts remain compatible with a local model later.
The cross-platform release entry point is:
python scripts/release.py build --version 0.1.0-alpha.11 --target windows-x64On an Apple Silicon Mac, the corresponding command is:
python3 scripts/release.py build --version 0.1.0-alpha.11 --target macos-arm64Release tooling will:
- verify a clean worktree and pinned submodules;
- run local tests;
- build and smoke-test the Windows package;
- require Authenticode signing for official Windows artifacts and Developer ID signing plus notarization for official macOS artifacts;
- generate checksums and a release manifest;
- upload an explicit versioned GitHub release from the local machine.
No release occurs implicitly after a push.