Tamir Duberstein 3fe19fcd81 Resolve subagent analytics connections lazily (#38165) ...

## Why

Subagent-start facts can arrive before their parent's connection context is
recorded, leaving later analytics events without client metadata.

## What changed

- Resolve a thread's connection by walking its parent-thread chain when the
  connection was not captured directly.
- Use the resolved connection for subagent setup, tool-call analytics, and
  completed turn events.

## Testing

Extend the subagent analytics test to start the child before the parent context
arrives and verify both command-execution and dynamic-tool-call events.

GitOrigin-RevId: c4d74a22de34abd6c6c5df1717a49ae0e1a9445d

2026-08-12 10:24:34 +00:00

..

src

Resolve subagent analytics connections lazily (#38165)

2026-08-12 10:24:34 +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