Separate user data from app binaries for safe upgrades #43
Description
TL;DR
Upgrading to a new version of Tasklog overwrites the SQLite database because user data lives alongside the app binaries. User data needs to be stored separately so upgrades don't destroy existing tasks.
Current State
The database (TasklogDatabase.db) is bundled inside the backend/ folder next to the exe. Extracting a new release replaces everything, including the user's data.
Desired State
User data is stored in a separate, user-accessible location (not buried in hidden folders). Upgrading the app replaces only binaries and config - existing tasks are untouched. First launch creates a fresh database if none exists; subsequent launches use the existing one.