setup-engine

Pinning a game engine version for reproducible builds involves recording the specific engine and version in your project's AGENTS.md and technology stack templates. This anchors the toolchain configuration so future builds match the documented setup.

When your pinned game engine version is newer than the model's training data, the setup detects this knowledge gap and triggers WebSearch. It fetches current references and migration notes to populate engine documentation with accurate information.

Updating engine reference docs after an upgrade requires analyzing knowledge gaps in the new version coverage. The setup generates or updates routing guidance and documentation to reflect the chosen engine, ensuring future upgrades follow documented migration paths.

Yes, the engine setup process works without external dependencies. It relies on internal configuration files like AGENTS.md and uses WebSearch capabilities to fill knowledge gaps when the pinned version exceeds the model's training data.

Agent routing must reflect the chosen game engine to ensure specialist agents follow the correct technical stack and documentation. This structured routing guides setup decisions and validates that docs accurately reflect the current toolchain.

The best way to document engine migration paths is to pin the version in AGENTS.md and update structured technical stack templates. This ensures future upgrades follow the documented migration paths and reference notes generated during setup.