Migration status

Avalonia is the only launcher UI. The previous Electron.NET host, React frontend, and IPC generator have been removed

Current implementation

Instance management, profiles, mod discovery and installation, news, and settings use native Avalonia views. Desktop calls Core interfaces directly; Local Node runs as a separate companion for autonomous sessions

See the architecture overview for current project ownership and packaging for release entry points

Remaining gaps

The first-run onboarding UI and per-instance log viewer are not implemented. Players create a profile and instance manually through First run, and inspect diagnostic files through the data directory

A visible settings field may preserve an older preference before a corresponding native feature is implemented. Check its consumers when documenting behavior

Existing data

Runtime compatibility remains for older profile, instance, configuration, and cache layouts. CoreMigrationRunner applies those migrations before Desktop creates view models that read player data. Completed durable steps are recorded in MigrationState.json; version-name enrichment is retried when source data becomes available

The native startup loading screen stays visible while local data migration completes

Migrations belong in Sources/Hyprism.Core/Migrations/ and need fixture-based tests. Hosts may invoke the runner, but must not contain migration rules

Do not restore the removed web bridge for new work. Historical implementation is available in version control when needed to understand old data