Summary
Make direct supported invocations of stateful integration and E2E tests use an isolated CODEX_HOME and state root, then clean those temporary artifacts.
Evidence
Historical temporary tracked-job session artifacts can be produced when individual stateful tests are invoked without the repository preload. This is distinct from issue #33, which covers inherited Claude host markers in test child environments.
Desired outcome
Direct test entrypoints are deterministic and cannot write persistent user state.
Acceptance criteria
- Every direct supported stateful test entrypoint selects an isolated CODEX_HOME and state root.
- Temporary state is cleaned after the test, including failure paths where supported.
- Add a regression proving no persistent user-state artifacts are created.
- Do not change production behavior.
Severity/release disposition
Medium test-isolation risk; backlog follow-up, not a production release blocker.
Provenance
Confirmed by the v1.7.4 reliability audit of direct stateful test execution; explicitly scoped separately from issue #33.
Summary
Make direct supported invocations of stateful integration and E2E tests use an isolated CODEX_HOME and state root, then clean those temporary artifacts.
Evidence
Historical temporary tracked-job session artifacts can be produced when individual stateful tests are invoked without the repository preload. This is distinct from issue #33, which covers inherited Claude host markers in test child environments.
Desired outcome
Direct test entrypoints are deterministic and cannot write persistent user state.
Acceptance criteria
Severity/release disposition
Medium test-isolation risk; backlog follow-up, not a production release blocker.
Provenance
Confirmed by the v1.7.4 reliability audit of direct stateful test execution; explicitly scoped separately from issue #33.