Use shared entry transition for bootstrap reconnect

[MhaWay]

Summary

• route bootstrap save-upload reconnect through the same Entry transition flow already used by Rejoiner
• extract a shared helper in Rejoiner so the Harmony-controlled return-to-entry path is implemented once
• keep the bootstrap reconnect waiting for Entry completion before reconnecting

Testing

• dotnet build .\Client\Multiplayer.csproj --configuration Release -v:q
• manual bootstrap test confirming save creation and reconnect flow complete without the return-to-menu crash

[MhaWay]

1.6, fix, standalone server

[Copilot]

Pull request overview

This PR routes the bootstrap save-upload reconnect path through the same “return to Entry” long-event transition used by the Rejoiner flow, aiming to avoid the return-to-menu crash and ensure reconnect only happens once Entry is fully reached.

Changes:

• Switch bootstrap reconnect from GenScene.GoToMainMenu() to a shared “return to Entry” transition and wait for Entry completion before reconnecting.
• Extract Rejoiner.ReturnToEntry(Action onFinished) and refactor DoRejoin() to reuse it.
• Stop the current multiplayer session before initiating the bootstrap reconnect.

Reviewed changes

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

File	Description
Source/Client/Windows/BootstrapConfiguratorWindow.BootstrapFlow.cs	Updates bootstrap save-upload reconnect to return to Entry via Rejoiner.ReturnToEntry and reconnect after Entry completes.
Source/Client/Session/Rejoiner.cs	Extracts a reusable ReturnToEntry helper and refactors DoRejoin to call it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.