Step 2: the telemetry seam

ITelemetrySink with the null, log and JSON Lines sinks, FTelemetryEvent and the envelope, TelemetryEvents,
UTelemetrySubsystem on the game instance, ASaltyGameMode minting the session id into the replicated
ASaltyGameState, bs.TelemetryTest, the git hash in the build string (D-42) and four Salty.Core.Telemetry tests
replacing the placeholder. Proved standalone and with a headless server plus client sharing one session id.

Also enables the engine's Editor, AutomationTest, GameplayTags, ConfigSettings and LiveCoding MCP toolsets
(D-43) so the editor's MCP server exposes more than the skills toolset.

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

Source/SaltyCore/Telemetry/TelemetryEvents.h

@@ -0,0 +1,15 @@
+#pragma once
+
+#include "CoreMinimal.h"
+
+// The event names. Every call site passes one of these to UTelemetrySubsystem::Emit; a literal at a call site is a
+// typo waiting for the analysis to find it. A name is added here, to the catalogue in Docs/Spec/Telemetry.md and to
+// the feature spec's Telemetry section in the same change as its first emit call, so the three never disagree.
+namespace TelemetryEvents
+{
+	// Session (step 2)
+	inline const FName AppStarted(TEXT("app_started"));
+	inline const FName SessionStarted(TEXT("session_started"));
+	inline const FName SessionEnded(TEXT("session_ended"));
+	inline const FName CheatUsed(TEXT("cheat_used"));
+}