ct-setup-projectlisted

# /ct-setup-project - Project Creation (Phase 3) **Primary request**: Use this skill when creating a CT project and toolchain with either a host or conversion toolchain. **Entry**: - `conversion`: `status` is `conf_generated` - `host`: `status` is `pending` or missing, `toolchain_mode=host`, and `toolchain_mode_user_confirmed=true` **Input**: `state.json` -> shared `toolchain_mode`, `source_info`, `project_inputs`; for `conversion`, also top-level `conf_path`, `artifacts.meta_ini_path`, `artifacts.meta_info_path`, `env_profile.resolved_vars`, and `env_profile.system_headers` (must already be populated as a non-empty list in Phase 1) **Output**: `state.json` (`status=project_created`, `ct_resources.*`, and either `host_toolchain` or `fingerprints`) **Execution mode**: In-memory state when called through `ct-orchestrator` / one-time `state.json` read in standalone mode **Standalone guard**: - If `toolchain_mode` is missing or unresolved -> **stop immediately** and tell the user to run `ct-init-project` first to complete project preparation - If it is `conversion` but `status` is not `conf_generated` -> **stop immediately** and tell the user to run `ct-init-project` first to complete project preparation - If it is `conversion` but `env_profile.system_headers` is missing or empty -> **stop immediately** and tell the user to run `ct-init-project` first to complete project preparation. `system_headers` must not be empty - If it is `host` but pre-Phase3 fields (`toolchain_mode_evi