Utterform 0.7.10 — Local diagnostics

Utterform now keeps useful, privacy-safe diagnostics for the complete application flow:
startup, recording and microphone setup, transcription, transformations, history and every
requested output. A run id and recording id connect related events. Operational failures shown
in the interface end with a short (ref …) value that identifies the matching log entry.

Logs remain on the device. There is no telemetry, analytics, automatic crash reporting or upload.
Utterform records operational metadata and outcomes, not transcripts, audio, prompts, clipboard
contents, API keys or response bodies. Keys, authorization material and home-directory prefixes
are redacted again when a line is written and when a support report is copied.

Settings → General → Support & diagnostics shows the actual platform log path and offers:

• Copy diagnostics — puts an agent-readable report of at most 256 KiB on the clipboard;
• Open log file — opens the current log with the system default application;
• Open log folder — reveals the file in Finder, Explorer or the Linux file manager.

The file target is resource-bounded: utterform.log rotates at 2 MiB, only
utterform.1.log and utterform.2.log are retained, and at most one bounded record waits in
memory. A full disk, removed directory or locked rotation can lose that record, but never blocks
recording and never grows an in-memory queue. Release builds keep INFO and above; debug builds
also keep DEBUG. Dependency logs are discarded.

Rust panics and unexpected WebView failures are recorded with bounded detail. A run marker reports
that the previous process did not reach a clean exit after a force-kill, power loss or native
crash; no platform crash dumps are collected. Version 0.7.10 makes the unavailable-marker case
consistent across Windows, Linux and macOS.

Verification scope

Validation covers formatting, redaction canaries, correlation references, bounded file rotation
and write-failure behaviour, copied-report limits and UTF-8 handling, frontend failure rate
limits, support actions, compact/light/dark layouts, and the existing application suite. The
release pipeline builds Linux x86-64, Windows x86-64 and macOS Apple Silicon, and publishes only
after every platform passes. Native open/reveal behaviour remains a real-desktop check.