Corewatch 0.1.1 — Logging and diagnostics

A small follow-up to 0.1.0 that makes problems easier to diagnose and report.

What's new

• Log file: logs are written to ~/.local/state/corewatch/logs/ (or $XDG_STATE_HOME). The file rotates daily and keeps the last 7 days.
• Startup banner: each log starts with the version, GTK/libadwaita runtime versions, distro, kernel, session type and whether it runs under Flatpak.
• Clear error reasons: every error has a short kind (io.not_found, io.permission, parse) plus its full cause chain.
• Less noise: a collector that keeps failing logs one warning, a summary every 60 seconds, and one line when it recovers. It no longer logs once per second.
• Crash reports: panics are logged with the thread name and a backtrace.
• Command-line options: --verbose / -v, --version / -V, --help / -h. You can also use the COREWATCH_LOG environment variable (e.g. COREWATCH_LOG=debug).
• When a module can't start, the empty page now suggests running corewatch --verbose for details.

Reporting a bug

Run corewatch --verbose from a terminal, or attach the latest file from ~/.local/state/corewatch/logs/.

Requirements

Unchanged: GTK ≥ 4.18 and libadwaita ≥ 1.7 (Debian 13 or newer, Arch, Fedora).