---
name: setup
description: Inspect a project and selectively enable Codex Engineering Platform with reversible local configuration.
---

Read the project's instructions first. Locate the installed `cep` runtime and
read `cep --help` for its actual command surface. The plugin distributes guidance
and assets; installing it does not install Python or grant provider access.

Use project inspection to discover repositories, toolchain markers, existing
instructions and ownership. Read the selected project commands before treating
them as usable. For Eventu, preserve `eventu-tooling` as the owner of setup and
project-specific skills; inspect it without applying changes.

Run installation as a dry run using this plugin's root as the bundle. Report
managed changes and conflicts. Apply only the requested project integration;
never copy the prototype or personal Codex configuration wholesale. An existing
authorization to set up this project covers ordinary reversible installation.
Keep credentials, browser identities, provider accounts and local paths private.

Detection proposes technology packs; activation is a project choice. Select only
the relevant pack IDs and agent roles in `engineering-platform.toml`. Unknown
stacks need a proposed and tested pack before unattended use. Shipped pack
commands are recipes, not evidence they work in this repository.

After applying, verify a repeated dry run is unchanged and check the actual
plugin/agent discovery in a fresh trusted project session. Project activation
does not establish native isolation or complete provider authentication. Report
those separately. Use runtime rollback/uninstall to preserve user edits.
If runtime qualification is blocked, stop before launching any autonomous worker
and keep the exact failed probe evidence. Plugin discovery is not qualification.