[Bug]: Codex chats started from Orca workspace do not appear in Codex Mac/CLI project history

### Operating system

macOS

### Orca version

1.4.40

### Details

**Short summary:**
Codex chats started from Orca are visible in Orca, but do not appear in Codex Mac app or Codex CLI in Warp for the same project.

**What happened?**
When I open a project in Orca, open Codex from Orca, start a chat, and rename it, the chat is visible inside Orca.

However, the same chat is not visible in Codex Mac app or normal Codex CLI on other terminals for that project.

Codex sessions started from a normal terminal/Warp inside the real project path are visible everywhere: Codex Mac app, Codex CLI/Warp, and Orca.

How can we reproduce it?
1. Open Orca.
2. Open a local project.
3. Open Codex from inside Orca.
4. Start a new chat.
5. Rename the chat.
6. Open Codex Mac app or Codex CLI/Warp for the same project.
7. Check whether the Orca-created chat appears in the project history.

Expected:
The Orca-created Codex chat should appear in Codex Mac app and Codex CLI/Warp history for the same project.

Actual:
The Orca-created Codex chat is visible in Orca, but not visible in Codex Mac app or normal Codex CLI/Warp history for the same project.

Anything else that might help:
Environment:
- Orca version: 1.4.40
- Codex Mac app version: 26.527.31326, build 3390
- Codex CLI version: 0.136.0
- macOS: 15.7.3, build 24G419
- Architecture: arm64

Local evidence:
Normal terminal-launched Codex sessions are recorded with cwd like:

/Users//path/to/project

Orca-launched Codex sessions are recorded with cwd like:

/Users//orca/workspaces//

Codex Mac app has the real project root saved/active:

/Users//path/to/project

So it looks like Orca-launched sessions are being associated with the Orca internal workspace path rather than the original project path.