# fix\(test\): keep codex replay recovery off the repo checkout · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/0b21b5d3c10c2aeca053e1da59e60f044ec68ecf)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 0b21b5d3c10c2aeca053e1da59e60f044ec68ecf

Requested commit: 0b21b5d3c10c2aeca053e1da59e60f044ec68ecf

Commit: 0b21b5d3c10c2aeca053e1da59e60f044ec68ecf

Tree: 20a1c536119ee9ee8633e36bb898bd12c49a8dd6

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(test): keep codex replay recovery off the repo checkout

The codex resume test was the only replay scenario without a
runtimePolicyOverride, so its checkpoint scope cwd fell back to
process.cwd() and baseline capture ran real git over the entire
checkout. Locally the capture short-circuits on checkpoint refs left
behind by earlier runs; on a fresh CI checkout it is a cold multi-second
capture that outlives the scenario wait budget, failing await_thread_idle
while the run is still mid-checkpoint. Point the fixture's turn/start
frames at the <workspace> placeholder and checkpoint a throwaway git
workspace like every other replay test.

Scenario waits are also wall-clock-bounded now: the iteration budget
counts event-loop turns, which burn at full speed while git/fixture IO
is in flight, so exhaustion additionally requires a 60s real-time
deadline to pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [81aeda113bb0f6fc6d60fff45d455f48671f08b0](https://git.cafe/pingdotgg/t3code/commit/81aeda113bb0f6fc6d60fff45d455f48671f08b0?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/0b21b5d3c10c2aeca053e1da59e60f044ec68ecf?format=markdown)