Quitting Obsidian during playback restores the position up to 5 s early #436

Quitting Obsidian while an episode plays restores the position from the last checkpoint, up to about 5 seconds before the quit.

Measured in real Obsidian 1.14.4 on Linux by the PR #427 verification (V-427d): playback closed at 41.03 s restored 35.19 s. Master before #427 behaves the same (41.09 s restored 35.25 s). A plugin disable or reload saves the exact position; only an app quit loses the tail.

Cause: by design since #376, PodNotes starts no data.json write after Obsidian's quit event and only waits for a write already in flight (src/main.ts, the quit handler). Obsidian's file adapter has no atomic replace, and a write cut short by the window closing truncates data.json. #376 reproduced that truncation for pagehide, so it chose to lose a few seconds of position rather than risk the file.

Possible fixes, to weigh against that risk:

• An atomic write (temp file plus rename via Node fs on desktop), which is the follow-up fix(persistence): never overwrite an unreadable data.json or write during window unload #376 named. After that, a quit task could save the final position safely.
• Confirm whether Obsidian always awaits quit tasks to completion before closing (no forced timeout), on desktop and mobile. If it does, a quit-task save is safe without atomic writes.

Severity: low. Up to one checkpoint interval of listening position on app quit; no other data is affected.