iceweasel-oai 6f6af0fce4 Record sandbox backends in command execution analytics (#47568) ...

## Why

Command execution analytics lack the observed sandbox backend. Older execution servers may omit this information, so an unknown backend must remain distinguishable from an explicitly unsandboxed process.

## What changed

- Carry optional `sandbox_type` metadata through command execution items and emit its metric tag as `sandbox_backend` in analytics.
- Propagate the observed backend through unified execution completion and failure events, including asynchronous exits.
- Preserve missing backend information as `None` and mark executed user shell commands as `Some(SandboxType::None)`.
- Exclude the metadata from serialized command items and generated schemas and TypeScript types.

## Testing

Extend tests for missing and explicit executor backends, backend propagation on failed execution, and analytics payloads, including platform-specific backend tags in app-server integration coverage.

GitOrigin-RevId: 178fe46824a6194910802ec02168ed40ee0b2019

2026-09-23 15:05:59 +00:00

..

fixtures

Remove CODEX_RS_SSE_FIXTURE test hook (#22413)

2026-05-13 03:08:01 +00:00

suite

Apply shared network policy throughout embedded Codex startup (#47411)

2026-09-23 00:49:19 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

event_processor_with_json_output.rs

Record sandbox backends in command execution analytics (#47568)

2026-09-23 15:05:59 +00:00