Port provenance: adapted from the pinned upstream source at 984023ddac0d5e27624f2baacde6105e45de375f under MIT; see the repository parity ledger for the exact path and blob.
Plan a compatible engine setup
This is a setup workflow and may be invoked only explicitly. It never installs,
enables, launches, or reconfigures anything during its inspection and proposal
phases.
- Run the read-only checks defined by
$ai-game-studio:toolchain-doctor.
- Detect existing Unity, Godot, Unreal, browser, and project evidence before
asking the user to choose an engine.
- Compare viable engines by project fit, platform export, team language,
maturity, performance, accessibility, license, install size, and existing
investment. Verify current terms before relying on them.
- Recommend one engine and one adapter. Do not activate more than one MCP server
for the same host application.
- Produce one transaction containing
plan_id, environment evidence, exact
actions, pinned sources, command arguments, downloads, licenses, permissions,
conflicts, backups, health checks, uninstall and rollback operations, expiry,
and digest.
- Show every file that would be materialized, including root and path-scoped
AGENTS.md, selected .codex/agents/*.toml, .ai-game-studio/project.json,
and .ai-game-studio/lock.json.
- Wait for explicit confirmation of the exact digest. Applying the transaction
is a separate operation. Changed evidence, an expired plan, or a digest
mismatch requires a new plan.
If the preferred route is unavailable on the detected OS, architecture, GPU, or
application version, first attempt a verified native adaptation. Otherwise show
a concise alternative comparison and ask the user to confirm the substitution.
Codex portability
Use the search, file-editing, shell, user-input, and subagent capabilities available in the active Codex surface. Use PowerShell syntax on Windows and POSIX syntax on macOS/Linux; do not require a Unix compatibility layer on Windows. Inherit the active model and permission mode, and do not weaken approval or sandbox boundaries.
1---2name: setup-engine3description: Configure the project's game engine and version. Pins the engine in AGENTS.md, detects knowledge gaps, and populates engine reference docs via web search when the version is beyond the LLM's training data.4---56> Port provenance: adapted from the pinned upstream source at `984023ddac0d5e27624f2baacde6105e45de375f` under MIT; see the repository parity ledger for the exact path and blob.78# Plan a compatible engine setup910This is a setup workflow and may be invoked only explicitly. It never installs,11enables, launches, or reconfigures anything during its inspection and proposal12phases.13141. Run the read-only checks defined by `$ai-game-studio:toolchain-doctor`.152. Detect existing Unity, Godot, Unreal, browser, and project evidence before16 asking the user to choose an engine.173. Compare viable engines by project fit, platform export, team language,18 maturity, performance, accessibility, license, install size, and existing19 investment. Verify current terms before relying on them.204. Recommend one engine and one adapter. Do not activate more than one MCP server21 for the same host application.225. Produce one transaction containing `plan_id`, environment evidence, exact23 actions, pinned sources, command arguments, downloads, licenses, permissions,24 conflicts, backups, health checks, uninstall and rollback operations, expiry,25 and digest.266. Show every file that would be materialized, including root and path-scoped27 `AGENTS.md`, selected `.codex/agents/*.toml`, `.ai-game-studio/project.json`,28 and `.ai-game-studio/lock.json`.297. Wait for explicit confirmation of the exact digest. Applying the transaction30 is a separate operation. Changed evidence, an expired plan, or a digest31 mismatch requires a new plan.3233If the preferred route is unavailable on the detected OS, architecture, GPU, or34application version, first attempt a verified native adaptation. Otherwise show35a concise alternative comparison and ask the user to confirm the substitution.3637## Codex portability3839Use the search, file-editing, shell, user-input, and subagent capabilities available in the active Codex surface. Use PowerShell syntax on Windows and POSIX syntax on macOS/Linux; do not require a Unix compatibility layer on Windows. Inherit the active model and permission mode, and do not weaken approval or sandbox boundaries.
frabcd