Codex confuses cwd with target worktree

Model often trips over the wd in which the Codex CLI thread has been started, and any new worktree it may have created in which it begins shipping new code. Later, as context fills, it regularly regresses to using the origin wd in which the convo was started, despite having (received direction to) worked in a new worktree.

Guardrails in agents.md don't appear to solve the issue.