Codex Cloud creates detached work checkout with no Git remote

Summary

Codex Cloud tasks are not receiving the requested Git checkout or remote even though the GitHub app has access to the repository and the branch is selected in the UI.

Reproduction

• Repository: elcartero07205-bit/ultron (private)
• Selected branch: codex/ar2c-os-isolated-bridge
• Reproduces in both an existing environment and a newly created environment.
• The fresh environment successfully installs all Python 3.12 dependencies from requirements.txt; this is not a package setup failure.

Expected

A cloud task should check out the selected branch and configure a usable origin remote.

Actual

Each task opens on local branch work at 8f0eaf7a08efae7f0aa8863c5d4a976cd72113bf. git remote -v returns no entries, only refs/heads/work exists, and the requested PR branch is absent. The task therefore cannot fetch, commit to, or push the PR branch.

Evidence

Fresh-environment read-only verification task: task_e_6a896a99be288325a85a331e1c32e7d3

It confirmed Python 3.12.13; all declared dependencies installed; offline pip install --dry-run --no-index -r requirements.txt succeeded; AR2C test modules collected successfully (21 + 90 tests). The only remaining failure is the missing Git remote and branch provision.

No credentials, secrets, or application data were used.

The issue names no source file or implementation entry point. Start by reproducing the fresh environment using task_e_6a896a99be288325a85a331e1c32e7d3 and inspect checkout state with git remote -v and the available refs; the Python 3.12 setup and requirements.txt installation already succeed. Done means the selected branch is checked out and a usable origin remote permits fetch, commit, and push.