import of onnxruntime on MacOS while undex Codex filesystem sandbox leaves :memory:.ses file in working directory

Nobody has claimed this yet.

### Describe the issue

On MacOS, if an import of onnxruntime occurs when run from within Codex CLI, then the onnxruntime telemetry initialization fails, and this leaves a spurious :memory:.ses file in the working directory.

### To reproduce

From within Codex CLI on MacOS, get the LLM to run

python -c 'import onnxruntime'

Then onnxruntime can't write to ~/Library/Application Support/Microsoft/DeveloperTools/.onnxruntime so it falls back to an SQLite :memory: and as a side effect of this leaves a spurious file called ':memory:.ses' in the working directory.

### Urgency

Really not very important. I just ran into this as markitdown imports onnxruntime and that's useful to use from within Codex.

The :memory:.ses file is innocuous, but was very confusing as this is sufficiently obscure that a web search didn't tell me what might be creating it.

### Platform

Mac

### OS Version

26.6.2

### ONNX Runtime Installation

Released Package

### ONNX Runtime Version or Commit ID

1.29.0

### ONNX Runtime API

Python

### Architecture

X64

### Execution Provider

Other / Unknown

### Execution Provider Library Version

_No response_

Start by reproducing `python -c 'import onnxruntime'` on MacOS from within Codex CLI, then trace the telemetry initialization and its SQLite `:memory:` fallback. The report names no source file or test; done means the import no longer leaves a `:memory:.ses` file in the working directory.

Written by the indexing model from the issue text.