Add Codex cloud environment setup

[Gonza10V]

Summary

• add an idempotent Codex cloud setup script for the GG Circuit pnpm/Cargo/Tauri monorepo
• install the Linux native libraries required to compile Tauri
• align Codex with CI by using Node.js 24, pnpm 10.12.1, and Rust 1.96.0 with clippy/rustfmt
• install dependencies with frozen/locked resolution, fetch the bundled Python runtime, build the frontend, and precompile Rust tests
• support a lighter cached-environment maintenance mode and a full --verify mode
• add AGENTS.md so Codex knows the repository structure and the correct frontend/Rust validation commands

Codex environment configuration

# Setup script
bash scripts/codex-setup.sh

# Maintenance script
bash scripts/codex-setup.sh --maintenance

Set the Codex environment Node.js package version to 24. The script will also select Node 24 through nvm or mise when available.

Validation

• bash -n scripts/codex-setup.sh
• reviewed commands against .github/workflows/typescript.yml and .github/workflows/rust.yml

The complete installation was not executed in this assistant sandbox because it has no outbound package-download access; the setup script is designed to run during the Codex setup phase, where internet access is available.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a5ad038d8f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid provisioning during verify mode

When --verify is used as the AGENTS.md “complete suite” after the Codex setup phase, this condition still runs install_system_dependencies, starting with apt-get update, before any checks execute. In cached task environments where package downloads are unavailable or sudo/root is not usable, verification fails even though the environment was already prepared; verify should skip provisioning like maintenance or split the check-only path from setup.

Useful? React with 👍 / 👎.