Hosted races stage properly: the owner no longer launches itself

Round five reached the race - full mesh on all three machines, eggs,
ACKs, mission running - but the owner raced ALONE. Cause: the engine
self-runs a pod at WaitingForLaunch when its console host is not
online (the arcade no-console fallback), and the owner''s in-process
console never connects to its own pod. On fast-loading owners the
self-run beat the console''s staging gate, so RunMission was never
sent and the members sat staged at black screens until someone hit
the & emergency-abort key.

gConsoleMarshalsLaunch (APPMGR) now tells the engine an in-process
console owns the launch: the network-race install sets it and the
owner holds at WaitingForLaunch with everyone else; plain single
player leaves it False and auto-runs as always. Verified on loopback:
all pods staged - RUN is back in the hosted-race log and both the
hosted race and the single-player cycle pass.

Also: unhandled-exception minidumps (rpl4crash.dmp beside the exe,
dbghelp loaded lazily) so test-machine crashes hand back stacks.

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

RP_L4/RPL4CONSOLE.cpp

@@ -531,6 +531,8 @@ void
 	gNetworkRace = False;
 	gRemotePodCount = 0;
 	gPilotNameCount = 0;
+	// single player launches itself (the engine's no-console self-run)
+	gConsoleMarshalsLaunch = False;
 	InstallCommon(mission_seconds);
 }
 
@@ -546,6 +548,10 @@ Logical
 	gRemotePodCount = 0;
 	gPilotNameCount = 0;
 
+	// the owner pod must stage at WaitingForLaunch with everyone else -
+	// this console launches the whole mesh at once
+	gConsoleMarshalsLaunch = True;
+
 	strncpy(gEggPath, egg_path, sizeof(gEggPath) - 1);
 	gEggPath[sizeof(gEggPath) - 1] = '\0';