v0.5.15

What's New in v0.5.15

Crash diagnostics

• More useful renderer-crash evidence — Geode now keeps bounded lifecycle, plugin-state, navigation, renderer-console, and process-metrics context around a renderer failure, along with a correlated incident ID and newly observed local Crashpad dump metadata.
• Local diagnostic export — use Help → Export Diagnostics… to create an allowlisted bundle containing the crash journal, rotated diagnostic logs, a sanitized manifest, and retained native minidumps.
• Safer retention and recovery — diagnostic logs rotate, crash journals and dumps remain bounded, Crashpad uploads stay disabled, and the existing one-time plugin-suppressed renderer recovery behavior is preserved.

Privacy note

The exporter does not intentionally read unrelated vault files, configuration, prompts, environment variables, IPC payloads, or plugin source. Console output and native minidumps can still contain sensitive fragments; inspect the exported directory before sharing it.

Known limitations

• Native dump symbolication may require the exact Electron and Geode build symbols.
• A real reproduction on the originally affected machine remains the best validation of diagnostic usefulness.
• macOS artifacts remain unsigned and unnotarized, consistent with previous Geode releases.

Full change: #70