docs(test): clarify hosted-service fault tests assert crash-isolation, not per-event resilience

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: HandyS11

tests/RustPlusBot.Features.Alarms.Tests/Hosting/AlarmsHostedServiceTests.cs

@@ -216,7 +216,8 @@ public async Task TriggeredLoop_survives_a_faulting_relay_and_StopAsync_complete
             await Task.Delay(20);
         }
 
-        // The relay threw; the loop swallowed it (LogTriggeredLoopFaulted) so StopAsync joins cleanly.
+        // The relay threw, causing the loop to fault and complete (LogTriggeredLoopFaulted). StopAsync joins the
+        // faulted task cleanly — no rethrow. This is crash-isolation, not per-event resilience.
         await h.Store.Received().GetAsync(10UL, serverId, 42UL, Arg.Any<CancellationToken>());
         await h.Service.StopAsync(default);
     }

tests/RustPlusBot.Features.Chat.Tests/Hosting/ChatHostedServiceTests.cs

@@ -99,7 +99,8 @@ await bus.PublishAsync(
             await Task.Delay(20);
         }
 
-        // The loop swallowed the fault (LogRelayLoopFaulted); StopAsync must join cleanly, not rethrow.
+        // The relay threw, causing the loop to fault and complete (LogRelayLoopFaulted). StopAsync joins the
+        // faulted task cleanly — no rethrow. This is crash-isolation, not per-event resilience.
         await poster.Received().PostAsync(Arg.Any<ulong>(), "Bob", "boom", Arg.Any<CancellationToken>());
         await service.StopAsync(default);
     }

tests/RustPlusBot.Features.Players.Tests/Hosting/PlayersHostedServiceTests.cs

@@ -106,7 +106,8 @@ await h.Bus.PublishAsync(new PlayerStateChangedEvent(
             await Task.Delay(20);
         }
 
-        // The loop swallowed the fault (LogRelayLoopFaulted); StopAsync must join cleanly, not rethrow.
+        // The relay threw, causing the loop to fault and complete (LogRelayLoopFaulted). StopAsync joins the
+        // faulted task cleanly — no rethrow. This is crash-isolation, not per-event resilience.
         await h.Sender.Received().SendAsync(
             10UL, Arg.Any<Guid>(), Arg.Is<string>(s => s.Contains("Bob")), Arg.Any<CancellationToken>());
         await h.Service.StopAsync(default);

tests/RustPlusBot.Features.StorageMonitors.Tests/Hosting/StorageMonitorsHostedServiceTests.cs

@@ -230,7 +230,8 @@ await h.Bus.PublishAsync(new StorageMonitorTriggeredEvent(
             await Task.Delay(20);
         }
 
-        // The relay threw; the loop swallowed it (LogTriggeredLoopFaulted) so StopAsync joins cleanly.
+        // The relay threw, causing the loop to fault and complete (LogTriggeredLoopFaulted). StopAsync joins the
+        // faulted task cleanly — no rethrow. This is crash-isolation, not per-event resilience.
         await h.Store.Received().GetAsync(Guild, serverId, 7UL, Arg.Any<CancellationToken>());
         await h.Service.StopAsync(default);
     }

tests/RustPlusBot.Features.Switches.Tests/Hosting/SwitchesHostedServiceTests.cs

@@ -255,7 +255,8 @@ public async Task StateLoop_survives_a_faulting_relay_and_StopAsync_completes_cl
             await Task.Delay(20);
         }
 
-        // The relay threw; the loop must have swallowed it (LogStateLoopFaulted) so StopAsync joins cleanly.
+        // The relay threw, causing the loop to fault and complete (LogStateLoopFaulted). StopAsync joins the
+        // faulted task cleanly — no rethrow. This is crash-isolation, not per-event resilience.
         await h.Store.Received().UpdateStateAsync(10UL, serverId, 42UL, true, Arg.Any<CancellationToken>());
         await h.Service.StopAsync(default);
     }