v0.3.9 — library refresh and faster update checks

Finished exports appear in the library straight away

A trim would show as completed in the queue, but the new clip wouldn't turn up in the library until you refreshed the page.

Completion was only detected as a change — a job had to already be visible as running when the "finished" message arrived. Anything that completed before the UI noticed it was skipped, so the library was never told to reload.

Exports hit this constantly: a trim is a stream copy that finishes in under a second, well inside the queue's five-second poll, so it usually appeared already completed and there was no change left to notice.

Completion is now recognised whenever a job is seen finished, not only at the moment it finishes. Verified: a trim refreshes the library within a second, with no reload.

Finished exports also said "Download complete!" — the queue stream wasn't passing along what kind of job it was. They now say "Export complete!".

Update checks are no longer slow to notice a release

A new release could stay invisible for up to seven hours — the server cached GitHub's answer for an hour, and the app only re-checked every six.

• Cache: 1 hour → 5 minutes
• Check interval: 6 hours → 30 minutes
• Re-checks whenever you return to the window, skipping the cache entirely

If the update indicator seemed slow to appear before, that's why.