[zjy-web222]

Reopening a completed conversation could count the time since the run began until the client observed the completed snapshot. The reproduced conversation showed 22 h 37 m 35 s instead of 57 m 35 s.

• Use the completion timestamp from the transcript for finished turns, including when an older cached end time exists.
• Seed recovered runs with the engine timestamp. Require the completed reply to follow the latest user prompt so the previous answer cannot settle a follow-up.
• Keep live ticking and the recorded stop or failure time. Prepare v0.50.36 for desktop release.

Validation:

• 171 focused Bun tests across transcript sync, activity state, assistant process rendering, and conversation engine adapters passed.
• App TypeScript check and maintainability audit passed.
• Electron Fraimz passed for the overnight re-open, active ticking, and stop. Run pnpm fraimz --flow conversation-elapsed-time --cdp-url http://127.0.0.1:9823 against the development desktop. The recorded frame shows the completed turn at 57 m 35 s.