Timestamps for the launch-chain logs (operator request)

Every relay/console print now carries a wall-clock prefix (_StampedOut
stdout wrapper; the GUI monitor regexes use search() so the prefix is
transparent), and the pod's READY/pend lines carry wall time + tick --
post-mortems measure delays instead of guessing (the 3m40s load
reconstruction needed heartbeat-counting archaeology).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

engine/MUNGA_L4/L4APP.cpp

@@ -577,7 +577,8 @@ int BTTakePendingRunMissions(void)
 	gBTRunMissionPendCount = 0;
 	if (pended > 0)
 		DEBUG_STREAM << "[launch] load complete -- firing " << pended
-			<< " pended RunMission(s)" << std::endl << std::flush;
+			<< " pended RunMission(s) t=" << GetTickCount()
+			<< std::endl << std::flush;
 	return pended;
 }
 
@@ -645,7 +646,8 @@ void
 		DEBUG_STREAM << "[launch] RunMission arrived in state "
 			<< (int)GetApplicationState()
 			<< " (still loading) -- pended until the load completes ("
-			<< gBTRunMissionPendCount << ")" << std::endl << std::flush;
+			<< gBTRunMissionPendCount << ") t=" << GetTickCount()
+			<< std::endl << std::flush;
 		return;
 	}