Surface a silent session reset in Ask Lucid

[ankitsejwal]

Completes the deferred bullet from #109 and closes the loop on #107: surface when the daemon silently answers from a fresh, memoryless session.

Why

The #107 fix (#110) makes the daemon's "resume produced nothing → restart fresh" fallback rare, but a genuinely dead/pruned handle still triggers it — and it was invisible: the phone got a normal-looking reply that had quietly lost the conversation. That silence is exactly how the original bug hid for a day. This makes the fallback observable end-to-end.

What

• Daemon flags the done frame with freshStart: true when it had a resume handle but fell back to a fresh session — both the coding path (runCodeTurn.ts) and the pod ask path (room/client.ts). It's set only when the user expected continuity (a resume was sent); a fresh-from-start turn is never flagged.
• Wire (@lucidity/shared): an optional freshStart on the done stream event.
• Phone:
  • roomClient threads freshStart into onDone meta and logs a session-reset diag event (red) so it shows in the diagnostics panel and counters.
  • The Lucid bubble shows a small amber note — "♻︎ Couldn't resume the earlier thread — answered from a fresh start (no memory of earlier messages)" — so the user learns immediately, instead of discovering it by quizzing the model's memory.
  • The Markdown export marks it too, so a pasted transcript reflects it.

Tests

• Daemon: the self-heal fallback test now asserts freshStart: true; the successful-resume and a new fresh-from-start test assert it's absent; the ask-path hang→retry test asserts the flag. Full suite 49/49.
• Mobile tsc --noEmit clean.

With this, the exact failure behind #107 — a reply that silently forgot the conversation — now says so on the bubble and logs a session-reset in diagnostics.