# Managed Codex verification timeout proof

Linux x64, Chromium 1280x800, light theme. Each app revision starts with its own fresh scenario home. The replay provider is the default; no paid model runs. The managed Codex packages are real official downloads with the installer's checksum checks intact.

Place the downloaded scenario beside the repository's scripts/scenarios/t3.ts. Compile stall.c as a shared library:

```sh
gcc -shared -fPIC -o /tmp/codex-verification-stall.so stall.c -ldl
```

Run from a current-main runner checkout, using the update scenario:

```sh
T3CODE_DEV_SEED=0 LD_PRELOAD=/tmp/codex-verification-stall.so CODEX_EVIDENCE_STALL_VERSION=0.169.0 T3_SCENARIO_INHERIT_ENV=LD_PRELOAD,T3CODE_DEV_SEED,CODEX_EVIDENCE_STALL_VERSION vp run scenarios:prove scripts/scenarios/managed-codex-verification-timeout.e2e.ts --base d7373c44feaa85f561c0f1e829ea1c31918acbeb --head f20ba2af796ea9d03a40abecaee5d6145bc64155 --upload-command 'ghdrop upload'
```

The hook makes global Codex --version detection fail to select managed installation. It delays execvp only for the managed staging runtime's codex --version, only when its official package manifest matches 0.169.0. Downloads, extraction, initial 0.166.0 installation, and all app code run normally. The hold is 100 seconds; the app's own 90-second verification timeout remains unchanged.

Steps: Settings > Providers > Add provider > Continue with ChatGPT > Continue; let pinned 0.166.0 install; cancel sign-in; click Continue with ChatGPT on that provider's card to update to 0.169.0; wait for held verification to fail. Compare the visible error, active.json, and staging cleanup. Neither run needed the triage's rollback or restart because the first update was stalled successfully.

For the supplemental fresh-install scenario, use fresh-install.e2e.ts and fresh-stall.c, omit CODEX_EVIDENCE_STALL_VERSION, and otherwise run the same comparison. This stalls verification of the pinned package on its first installation.
