OpenOats 1.86.0 — failures that used to be silent

This release is almost entirely the work of one external contributor, @thunter009, who found and fixed a run of failures that all shared a shape: something went wrong and OpenOats said nothing.

Notes generation no longer fails silently

• Reasoning models no longer break notes entirely (#704). A model returning "content": null with its output in a sibling reasoning field threw in the JSON decoder and killed notes generation. Both the streaming and non-streaming paths now handle it, and a stream that delivers only reasoning reports that instead of quietly handing back empty notes. Empty generated notes are now treated as a failure rather than a result.
• Failed automatic notes generation now tells you (#707). The failure was recorded only as a diagnostics breadcrumb, which is gated behind a setting that defaults to off — so on a stock install a failed notes call wrote nothing anywhere. It now retries once, then posts a notification. This also fixed a latent bug where tapping any OpenOats notification body could start a recording.
• LLM HTTP errors now include the server's explanation (#716). Local LLM API error (HTTP 404) gave you nothing to act on, even though the response body names the cause — an Ollama 404 says which model is missing. The message now carries it.

Recording and storage

• Transcript write failures are now visible (#712). The error channel for failed live-transcript writes was populated but read by no view, so a recording that was not reaching disk looked normal.
• Notes-folder exports retry instead of vanishing (#710). A mirror that failed while the folder was unreachable — a network share that was down, say — was never recorded and never retried. Pending exports now survive a relaunch and heal on the next meeting event, bounded by a per-session backoff.

Meetings and calendar

• Better calendar event matching (#706). The session-to-event binding was chosen at minute zero from a ±15-minute window, so a recording starting in the tail of the previous meeting bound to that meeting. It is now re-resolved at finalize against the session's real interval, which also corrects speaker-name seeding, folder routing, and template selection.
• Custom meeting apps are now editable in Settings (#709). The setting already existed and was already respected, but was reachable only by defaults write plus a relaunch. Browser-based calls can now be detected by adding the browser's bundle ID; edits apply without restarting the app.

Notes

• My Notes stays reachable after notes are generated (#713). The scratchpad was hidden once a session had AI notes, including for older sessions where the text was still on disk. It now appears as a collapsible section above the generated notes. Reported by @gthay.

---

Contributors: @thunter009 (#704, #706, #707, #709, #710, #712) — thank you. Issues reported by @gthay (#713) and @willoneal (#716).