fix: route the network components so they actually attach

The diagnostic icons answered it. The wrench was present, so AddBase and
the Overrides had applied correctly all along -- but the thermal-missile
and resource icons were both showing, meaning both NetworkValues read
zero. With both signals absent, VentAllowed collapses to true and
AutoPowerToggle degenerates to plain PowerToggle: on means permanently
on, exactly as reported.

A network component is only attached to the network if a route reaches
it. The part's NetworkPort anchors on one component and a NetworkRouter
bridges that anchor to the rest -- which is how vanilla connects the
radiator's own NetworkedThermalDissipationLoadValue, and how the thermal
amplification pump reaches the resonance beam turret.

Add routes from each part's anchor: NetworkedHeatBuffer on the radiator
via its existing Router, and a new NetworkRouter on the thermal battery,
the missile launcher and base_part_overclock, none of which ships one.

Unrouted network components are not an error -- they simply never
connect and read as absent forever, which is why three versions loaded
cleanly and did nothing. The new test fails on any network component the
mod adds that no route names.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011oLWY1G6S8U35bi2FxVWni

components/launcher_ammo_signal.rules

@@ -34,3 +34,22 @@ AutoRad_NetworkedThermalAmmo
 	Categories = [ auto_radiator_ammo_user ]
 	IncludeInBlueprints = false
 }
+
+// Routes the broadcast onto the heat network. NetworkHeatOutputProxy is what
+// the launcher's thermal ports anchor on. Those ports are only operational in
+// thermal missile mode, so a launcher loaded with anything else is simply not
+// on the network -- which is the behaviour we want anyway.
+AutoRad_Router
+{
+	Type = NetworkRouter
+	RouteGenerators
+	[
+		{
+			Type = Bidirectional
+			Routes
+			[
+				[NetworkHeatOutputProxy, AutoRad_NetworkedThermalAmmo, 0]
+			]
+		}
+	]
+}

components/overclock_overflow_signal.rules

@@ -46,3 +46,21 @@ AutoRad_NetworkedForceVent
 	Categories = [ auto_radiator_force_vent ]
 	IncludeInBlueprints = false
 }
+
+// Routes the broadcast onto the heat network. NetworkHeatInput is what this
+// base's thermal ports anchor on (BASE_THERMAL_PORT: RouteSource =
+// &../HEAT_NETWORK_INPUT).
+AutoRad_Router
+{
+	Type = NetworkRouter
+	RouteGenerators
+	[
+		{
+			Type = Bidirectional
+			Routes
+			[
+				[NetworkHeatInput, AutoRad_NetworkedForceVent, 0]
+			]
+		}
+	]
+}

components/thermal_battery_vent.rules

@@ -90,3 +90,24 @@ AutoRad_NetworkedHold
 	Categories = [ auto_radiator_hold ]
 	IncludeInBlueprints = false
 }
+
+// A network component is only actually attached to the network if a route
+// reaches it. The part's NetworkPort anchors on one component -- here
+// NetworkedHeatStorage -- and a NetworkRouter bridges that anchor to every
+// other network component on the part. The thermal battery ships no router,
+// because vanilla has nothing else to reach, so the broadcast above needs one
+// or it is never connected to anything and reads as absent.
+AutoRad_Router
+{
+	Type = NetworkRouter
+	RouteGenerators
+	[
+		{
+			Type = Bidirectional
+			Routes
+			[
+				[NetworkedHeatStorage, AutoRad_NetworkedHold, 0]
+			]
+		}
+	]
+}