Mech: THE 0xBD3 UNTANGLE -- real SubsystemMessageManager in [0x10d], the mapper's one true home is roster slot 0 (task #7)

Binary census [T1]: mech+0x434 has exactly 2 writers (ctor init + factory
case 0xBD3) and ONE reader (@0x4b984b in MechWeapon::SendDamageMessage
@004b9728) -- pure message-manager semantics, nothing mapper-like.  The
factory case now builds the real SubsystemMessageManager (ctor @0049bca4,
0x130, ConsolidateAndSendDamage Performance); the misbuilt MechControlsMapper
squatter is evicted.  Every mapper consumer re-pointed to MappingMapper()
(roster slot 0 = the binary's **(mech+0x128); SetMappingSubsystem @0049fe40
touches ONLY slot 0 -- its [0x10d] mirror removed).  Non-viewpoint mechs get
a slot-0 demand LATCH (base mapper, [T3] accommodation -- the binary leaves
slot 0 NULL off-viewpoint but never drives/animates those paths; ours does).
Verified: solo drive+gait clean; MP replicant gait through the latch (full
run lifecycle); 3x kill/respawn cycle with type-6 records on the observer.
Remaining (task #7 tail): the messmgr's consolidated TakeDamageStream send +
weapon-path routing (@004b9728 real body).

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

game/reconstructed/messmgr.cpp

@@ -486,3 +486,17 @@ void
 // resources beyond the base.
 //
 // SubsystemMessageManager::DamageInformation::~DamageInformation() {}  // @0049c3e3
+
+//###########################################################################
+//					CreateMessageManagerSubsystem -- factory bridge (task #7)
+//
+//	mech.cpp's streamed-subsystem factory (case 0xBD3) calls this in the
+//	house complete-type-TU pattern (cf. CreateEmitterSubsystem et al).
+//
+Subsystem *CreateMessageManagerSubsystem(Mech *owner, int id, void *seg)
+{
+	return new (Memory::Allocate(0x130)) SubsystemMessageManager(
+		owner, id,
+		(SubsystemMessageManager::SubsystemResource *)seg,
+		SubsystemMessageManager::DefaultData);
+}