Best possible solution:

Land this PR after maintainer review and CI, then close #82164 as fixed by the merged cron/session identity change.

Do we have a high-confidence way to reproduce the issue?

Yes, at source level: the docs define current as context-aware, and current main persists the cron session entry without adopting rotated embedded-runner session id/file metadata before the next user turn. I did not run a live Telegram flow.

Is this the best way to solve the issue?

Yes: adopting the embedded runner's final session id/file at cron finalization is the narrowest maintainable fix, and carrying sessionFile through error metadata covers compact-then-fail paths without channel-specific policy.

Acceptance criteria:

• node scripts/run-vitest.mjs src/cron/isolated-agent.session-identity.test.ts src/cron/isolated-agent/run-session-state.test.ts src/agents/pi-embedded-runner/run/helpers.test.ts
• git diff --check

What I checked:

• Protected PR state: The provided GitHub context shows labels maintainer and proof: override, so conservative cleanup should not close this PR and the real-behavior proof gate is explicitly overridden.
• Current main persistence path: On current main, finalizeCronRun reads finalRunResult.meta?.agentMeta for usage/model/CLI-session data and then calls prepared.persistSessionEntry(), but it does not adopt agentMeta.sessionId or agentMeta.sessionFile into the cron session entry before persistence. (src/cron/isolated-agent/run.ts:852, 29b5563ccda2)
• Current main reports the original run id: prepareCronRunContext captures runSessionId before execution and current main's withRunSession returns that original value, so a rotated transcript identity is not reflected in the final cron result. (src/cron/isolated-agent/run.ts:581, 29b5563ccda2)
• Documented cron contract: The cron docs describe current as bound at creation time for context-aware recurring work and direct users to current or session:<id> when a recurring job should build on the same conversation context. Public docs: docs/automation/cron-jobs.md. (docs/automation/cron-jobs.md:91, 29b5563ccda2)
• Embedded runner metadata contract: EmbeddedPiAgentMeta already includes optional sessionFile, and the successful embedded-runner path reports both sessionId and sessionFile, which supports using that metadata during cron finalization. (src/agents/pi-embedded-runner/types.ts:10, 29b5563ccda2)
• PR adoption path: The PR diff adds adoptCronRunSessionMetadata, normalizes run metadata, updates session id/file plus usage-family ids, and calls it from finalizeCronRun before persistence. (src/cron/isolated-agent/run-session-state.ts:66, 34c0354af3fa)

Likely related people:

• steipete: Current-main history shows Peter Steinberger recently touched the cron runtime path and introduced the current session persistence helper surface that this PR updates. (role: recent area contributor; confidence: high; commits: 38e53a89b256, b4f6cb29b846; files: src/cron/isolated-agent/run.ts, src/cron/isolated-agent/run-session-state.ts, src/agents/pi-embedded-runner/run/helpers.ts)
• jalehman: Josh Lehman authored prior cron context-engine/session-key work across the same isolated-agent session-state and runner files, making him a useful secondary reviewer for session continuity semantics. (role: feature-history contributor; confidence: medium; commits: a3c51f91c58a, 4004c9342d7d; files: src/cron/isolated-agent/run-session-state.ts, src/cron/isolated-agent/run.ts, src/agents/pi-embedded-runner/run.ts)

Remaining risk / open question:

• I did not run the focused Vitest files or a live scheduled chat flow in this read-only review; the PR body reports focused test output and the maintainer proof override covers the real-behavior gate.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 29b5563ccda2.