fix(cloud-agent): propagate taskRunId through codex loadSession

[tatoalo]

Problem

newSession and unstable_resumeSession both carry _meta.taskRunId / taskId into sessionState and emit _posthog/sdk_session on cloud runs. loadSession dropped them on the floor. Re-attaching a desktop client to an existing cloud codex session therefore silenced TURN_COMPLETE and USAGE_UPDATE on subsequent prompts (both gated on sessionState.taskRunId), and the adapter→session mapping was never published.

Changes

In CodexAcpAgent.loadSession, propagate taskRunId / taskId into sessionState and fire _posthog/sdk_session when taskRunId is present, matching the other session-creation paths.

How did you test this?

• Two new unit tests: taskRunId is propagated and SDK_SESSION fires when present; no extNotification is emitted when taskRunId is absent.
• Full @posthog/agent suite green.

[tatoalo]

• fix(cloud-agent): serialize concurrent codex prompts to fix usage accounting #1721
• fix(cloud-agent): propagate taskRunId through codex loadSession #1720 👈 (View in Graphite)
• fix(cloud-agent): inject prContext into codex prompts #1719
• fix(cloud-agent): broadcast user prompt on codex cloud runs #1718
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[tatoalo]

Merge activity

• Apr 20, 9:45 AM UTC: @tatoalo merged this pull request with Graphite.