Adds a "Nach Updates suchen" button to the settings' new Updates section,
next to the app's own version. It runs check_for_update_now, the very same
feed check the background loop uses (one implementation, shared via
UpdateSchedule), so a manual check counts as an attempt for the same
scheduler: success resets the 6 h interval and the failure count, a failure
advances the backoff by one step, and a manual and a background check never
run at the same time (serialized).
An available update leaves the same state the background check does, so the
main window's banner still shows it; the settings also show it inline with
the existing "Installieren & neu starten" button and busy guard/hint. "None"
and "error" results are shown inline (unlike the background check, which
never surfaces its errors). On Linux (can_self_update) the button still asks
the feed but offers no install, since Debian builds never self-update.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- the backend URL is no longer a setting: one constant per build
(release/dev) in src-tauri/src/backend.rs; Settings shows the server
read-only; an old backend_url in settings.json is ignored
- the stored key records the backend it was created for; a key of
another backend is discarded before any use and never stored
- a refused key is discarded only if it still is the stored one
- the keyring is never called while the settings are locked
- one upload per call at a time, also visible after a view switch
- opener plugin without its link-click script (it also ran in the
remote login page); a login error says to reload the login page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Settings section "Backend": backend URL, login status checked live
(logged in as / until, not logged in, backend unreachable), Anmelden /
Neu anmelden, Abmelden and the link to the key management page
- login window "backend-login": the backend's own login page in an
incognito webview without any Tauri capability; after a page load
behind the login, its cookies create a key (one request, never stored
or logged), the key goes to the keyring, the window closes; closing it
cancels; one login at a time, later requests wait for the same result
- call detail: "Transkript hochladen" / "Erneut hochladen" (with a
confirmation), "wird hochgeladen…", "Hochgeladen am … (ID …)" and
inline errors; logs in first when there is no usable key
- saving a different backend URL discards the key of the old backend
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Summaries are not coming to the desktop app, and the customer is chosen
in the web UI after the upload:
- drop the Anthropic key (Service::Anthropic, Settings field) and delete
a leftover keyring entry best-effort at startup
- drop the Summary model, the store's summary accessors and the
"Zusammenfassung" tab; the transcript is the detail's only content
- drop the mocked customer accounts, list_accounts/set_account and the
"Kunde" dropdown; calls.account_id and summaries stay in the schema
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>