Network races: the local console marshals remote pods over the wire

The lobby-owner-as-console architecture, in-engine. RPL4CONSOLE gains
RPL4LocalConsole_InstallNetworkRace: the owner pod switches to network
mode and meshes like any pod (egg fed locally via FeedLocalEgg, which
now opens the ConsoleOnly state gate), while the console tick also
marshals REMOTE pods over NetTransport speaking the exact arcade
protocol - egg chunks with 5s-retry-until-ACK, 1Hz state polling,
RunMission once every pod stages at WaitingForLaunch, StopMission at
expiry (remotes first, local pod holds until their EndMission scores
land), score intake labeled with [pilots]-order names on the results
screen.

The front end builds the multi-pilot egg: RP412HOSTPODS lists member
console channels (lobby stand-in; the Steam lobby feeds the same
path), RP412HOSTPORT/RP412HOSTADDR set the owner side.

Winsock Connect now redials with a fresh socket per attempt (a refused
TCP socket is dead; the old loop reused it) bounded at 120s - needed
whenever a peer boots after the caller, which is the normal Steam
lobby launch order.

Verified on loopback: member pod in -net, owner hosting from its menu;
mesh completed both sides, 30s race, remote score collected over the
wire (host 3), local stop after the drain, results screen shows both
pilots by name in one process that returns to the menu.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

MUNGA_L4/L4NET.CPP

@@ -378,6 +378,11 @@ void
 	Register_Object(networkEggNotationFile);
 	networkEggNotationFile->WriteFile("last.egg");
 
+	// In network mode (the owner pod of a multiplayer race) the state
+	// gate must open or CheckBuffers keeps dropping mesh packets - a
+	// console-fed pod gets this from the chunked egg path instead.
+	currentNetworkState = NormalState;
+
 	ReceiveEggFileMessage egg_message(-1, 10, "local egg", 10);
 	application->Post(DefaultEventPriority, this, &egg_message);
 }