Problem

Live Telegram had an already-corrupted session store entry where sessionId was d2b274... but sessionFile still pointed to e21b2a10...jsonl. The first reset fix only rewrote transcript files whose basename matched the previous session id, so it preserved this stale UUID transcript and kept replaying old history.

Acceptance

• sessions.reset creates a new transcript file for default UUID-shaped JSONL paths that do not match the current session id.
• Custom non-default transcript paths, such as owned child transcript files, remain preserved.
• A regression test covers the mismatched UUID file case observed on Zeus.