macOS 0.4.0 install reports bundle version 0.3.0

[felixhaeberle]

Summary

After fully removing Flashtype 0.3.0 and reinstalling Flashtype 0.4.0, macOS hang diagnostics still report the installed /Applications/Flashtype.app as version 0.3.0 (0.3.0).

This looks like stale macOS bundle/version metadata in the 0.4.0 build rather than a stale local install, because the previous 0.3.0 app and related artifacts were wiped before reinstalling.

Observed behavior

A fresh install expected to be 0.4.0 produces a macOS hang report with:

Command:     Flashtype
Path:        /Applications/Flashtype.app/Contents/MacOS/Flashtype
Identifier:  com.flashtype.app
Version:     0.3.0 (0.3.0)
Event:       hang
Duration:    57.78s
Note:        process was unresponsive for 54 seconds before sampling

Expected behavior

A clean 0.4.0 install should report 0.4.0 in macOS diagnostics, for example:

Version: 0.4.0 (0.4.0)

Why this matters

If macOS reports the wrong version, crash/hang diagnostics are misleading and it becomes hard to know which release actually produced a report.

Additional diagnostic context

The same report also shows the app hanging on the Electron main thread during Lix open/sync work:

NativeLix::open_fs
lix_sdk::filesystem::sync_disk_to_lix
lix_engine::session::execute
lix_engine::transaction::commit
lix_engine::transaction::validation::validate_prepared_writes
lix_engine::live_state::reader::scan_rows
lix_engine::tracked_state::scan_rows_at_commit
SqliteRead / collect_unique_values / visit_keys

That hang may be a separate issue, but the version metadata problem makes it harder to triage correctly.

Suspected area

Please check the release/build metadata used for the macOS bundle, especially Info.plist values such as CFBundleShortVersionString and CFBundleVersion, plus any Electron Builder/Sparkle metadata that could still be set to 0.3.0.