Postpone initialization to after UI has sent Ready event

[DocMoebiuz]

We now wait for the UI to signal that the progress bar is ready. Only then we will continue with the rest of the initialization.

Background:

• Users reported that sometimes the splash screen would not advance.
• Assumption: the initialization is faster than loading the frontend, and the frontend misses messages from the backend.
• This fix makes sure that the UI is ready to receive messages from the backend.

fixes #2864

[github-actions]

Build for this pull request:
MobiFlightConnector.zip

[Copilot]

Pull request overview

This PR introduces a frontend→backend “ready” handshake so the backend postpones publishing startup/progress messages until the /start UI route is ready to receive them, addressing the reported stuck splash/start loop (fixes #2864).

Changes:

• Add a new CommandFrontendState command type and send it from the /start UI when mounted.
• Subscribe to CommandFrontendState in MainForm and move main initialization work to run after the frontend signals ready.
• Register the new incoming command type in the backend project.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/MobiFlightConnector/frontend/src/types/commands.d.ts	Adds CommandFrontendState to the frontend command type system.
src/MobiFlightConnector/frontend/src/components/StartupProgress.tsx	Publishes CommandFrontendState (ready) from the /start route.
src/MobiFlightConnector/UI/MainForm.cs	Defers backend initialization until the frontend sends ready.
src/MobiFlightConnector/MobiFlightConnector.csproj	Includes the new backend incoming command class in compilation.
src/MobiFlightConnector/MobiFlight/BrowserMessages/Incoming/CommandFrontendState.cs	Defines backend payload type for the new frontend state command.

[github-actions]

Build for this pull request:
MobiFlightConnector.zip

[Copilot]

Pull request overview

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/MobiFlightConnector/UI/MainForm.cs:510

• OnFrontendReady is triggered by an incoming WebView message and is async void without any exception handling. If anything throws during initialization, it can crash the UI thread and frontendReady will stay true, preventing any retry. Wrap the body in try/catch with Log.Instance.log(..., LogSeverity.Error) and consider only setting frontendReady (or an initialized flag) after successful initialization (or resetting it on failure).

        private async void OnFrontendReady(object sender, EventArgs e)
        {
            if (Properties.Settings.Default.Started == 0)
            {
                OnFirstStart();
            }

[github-actions]

Build for this pull request:
MobiFlightConnector.zip