Release v0.1.7 - Auto-update works + Task Manager autostart · BENZOOgataga/Tideline

The auto-update path actually surfaces newer releases now, and Auto-start is wired through HKCU\Run so Tideline lives where Task Manager expects it.

Auto-update fixed

Workflow now uploads releases.win.json + assets.win.json per channel. Velopack 0.0.1298's GithubSource parser reads those (the legacy RELEASES file alone returned "No remote full releases found"). From v0.1.7 onward the in-app banner will actually appear when a newer release is out.
Settings -> About no longer freezes on "Checking..." after a manual check. UpdateService.CheckCompleted event drives a refresh.

Tideline now appears in Task Manager -> Startup apps. Toggling there mirrors into Settings -> Auto-start and vice versa.
App self-delays 8 seconds on logon (--startup arg) so it does not compete with other auto-start programs for boot resources. Quietly lands in the tray, no main window.
Startup row reads Tideline for release builds, Tideline Development for Debug builds, so two side-by-side installs never collide.
One-time migration: if you had Auto-start enabled on v0.1.6 or earlier (it used a Task Scheduler entry), v0.1.7 detects the legacy Tideline-AutoStart task on first launch, creates the equivalent HKCU\Run entry, and sweeps the task. A marker under %LocalAppData%\Tideline prevents the check from running again.

Check for updates is no longer disabled. Triggers a fresh feed query (bypasses the once-per-session guard).

Local-first SQLite. The Velopack update check is the only outbound network call. No telemetry, no accounts, no cloud sync.

v0.1.6 and earlier installs still have the broken Velopack locator and cannot self-update. Reinstall from Tideline-win-Setup.exe below once.

Full Changelog: v0.1.6...v0.1.7