iceweasel-oai eb078b4f44 Preserve target-native cwd in permission approval requests (#42314) ...

## Why

Permission requests can originate in an environment whose path convention differs from the Codex host. Requiring the request working directory to be host-native prevents those requests from reaching interactive approval.

## What changed

- Carry the request `cwd` as a `LegacyAppPathString` through core events and the app-server protocol so the target environment's native representation is preserved.
- Convert the preserved value back to a `PathUri` when materializing permission grants.
- Regenerate the JSON and TypeScript protocol schemas for the updated `cwd` type.

## Testing

- Exercise the app-server permission request round trip with a target-native working directory across host path conventions.
- Verify remote permission requests retain their environment working directory and granted access still unblocks later execution.

GitOrigin-RevId: 97dc9707d9048883d20bab1b69c93871039f3188

2026-09-02 17:27:50 +00:00

..

src

Preserve target-native cwd in permission approval requests (#42314)

2026-09-02 17:27:50 +00:00

BUILD.bazel

Extract codex-analytics crate (#15748)

2026-03-25 11:08:05 -07:00

Cargo.toml

[codex-analytics] emit goal lifecycle analytics (#27078)

2026-06-09 18:45:54 -07:00