Normalize per-pump alert-emission test suites to Trio Alert Emission prefix

TrioTests/DanaKitAlertEmissionTests.swift

@@ -34,7 +34,7 @@ import Testing
 /// (N1 Hardware Fault catch-all -> `.critical`) is registered `.timeSensitive`
 /// — so a daily/basal hard stop or an unrecognized pump alarm reaches the user
 /// below critical.
-@Suite("Manager Emissions: DanaKit") struct DanaKitAlertEmissionTests {
+@Suite("Trio Alert Emission: DanaKit") struct DanaKitAlertEmissionTests {
     private func id(_ manager: String, _ alertID: String) -> Alert.Identifier {
         Alert.Identifier(managerIdentifier: manager, alertIdentifier: alertID)
     }
@@ -214,7 +214,7 @@ import Testing
 /// (`DanaKit/Packets/DanaNotifyAlarm.swift`,
 /// `DanaKit/PumpManager/*.swift`, `DanaKit/Packets/DanaBolusStart.swift`,
 /// `DanaKitUI/*`, `Common/NotificationHelper.swift`).
-@Suite("Message Classification: DanaKit") struct DanaKitMessageClassificationTests {
+@Suite("Trio Alert Emission: DanaKit — Classification") struct DanaKitMessageClassificationTests {
     /// An error whose `String(describing:)` is exactly the catalogued display
     /// string, so the classifier matches over the real natural-language text.
     private struct StubError: Error, CustomStringConvertible { let description: String }

TrioTests/MedtrumKitAlertEmissionTests.swift

@@ -29,7 +29,7 @@ import Testing
 /// hourly suspend) reach the user only at the UN-notification default level
 /// (treated as `.timeSensitive` — unknown -> assume time-sensitive),
 /// below their `.critical` taxonomy mapping.
-@Suite("Manager Emissions: MedtrumKit") struct MedtrumKitAlertEmissionTests {
+@Suite("Trio Alert Emission: MedtrumKit") struct MedtrumKitAlertEmissionTests {
     private func id(_ manager: String, _ alertID: String) -> Alert.Identifier {
         Alert.Identifier(managerIdentifier: manager, alertIdentifier: alertID)
     }
@@ -179,7 +179,7 @@ import Testing
 /// and the BLE "timeout" strings. Notably the occlusion notification body is
 /// misspelled "occlussion" (double-s), which does NOT contain "occlusion" and
 /// thus mis-routes to `.other`.
-@Suite("Message Classification: MedtrumKit") struct MedtrumKitMessageClassificationTests {
+@Suite("Trio Alert Emission: MedtrumKit — Classification") struct MedtrumKitMessageClassificationTests {
     /// `String(describing:)` returns `description` verbatim, reproducing the
     /// exact text the classifier's substring matcher sees.
     private struct StubError: Error, CustomStringConvertible {

TrioTests/MinimedKitAlertEmissionTests.swift

@@ -26,7 +26,7 @@ import Testing
 /// intended registry entry ("Minimed","PumpReservoirEmpty"=.critical) is
 /// unreachable under the emitted managerIdentifier "Minimed500" — so an
 /// out-of-insulin condition never escalates to a critical interruption.
-@Suite("Manager Emissions: MinimedKit") struct MinimedKitAlertEmissionTests {
+@Suite("Trio Alert Emission: MinimedKit") struct MinimedKitAlertEmissionTests {
     private func id(_ manager: String, _ alertID: String) -> Alert.Identifier {
         Alert.Identifier(managerIdentifier: manager, alertIdentifier: alertID)
     }
@@ -136,7 +136,7 @@ import Testing
 /// (`MinimedKit/...`). Each row pins CURRENT behavior (must be green) and the
 /// gap ratchet below fails when the classifier is improved to map the
 /// taxonomy-intended messages.
-@Suite("Message Classification: MinimedKit") struct MinimedKitMessageClassificationTests {
+@Suite("Trio Alert Emission: MinimedKit — Classification") struct MinimedKitMessageClassificationTests {
     private struct StubError: Error, CustomStringConvertible { let description: String }
 
     struct Row {

TrioTests/OmnipodKitAlertEmissionTests.swift

@@ -38,7 +38,7 @@ import Testing
 // Classifier-channel gaps: podSuspended, noResponse, podNotConnected, unfinalizedBolus
 // all land at .active where taxonomy wants .timeSensitive.
 
-@Suite("Manager Emissions: OmnipodKit") struct OmnipodKitAlertEmissionTests {
+@Suite("Trio Alert Emission: OmnipodKit") struct OmnipodKitAlertEmissionTests {
     // MARK: Helpers
 
     private func id(_ manager: String, _ alertID: String) -> Alert.Identifier {
@@ -246,7 +246,7 @@ import Testing
 // The gap ratchet fails the moment the classifier improves (a gap row starts
 // hitting a real bucket), forcing this file to be updated.
 
-@Suite("Message Classification: OmnipodKit") struct OmnipodKitMessageClassificationTests {
+@Suite("Trio Alert Emission: OmnipodKit — Classification") struct OmnipodKitMessageClassificationTests {
     /// Error whose String(describing:) is exactly `description`, so the substring
     /// classifier matches over the supplied display text verbatim.
     private struct StubError: Error, CustomStringConvertible {

TrioTests/RileyLinkKitAlertEmissionTests.swift

@@ -38,7 +38,7 @@ import Testing
 /// (`.active`) as designed. There is NO dominant critical-tier miss because
 /// RileyLinkKit emits no Critical alerts. Per the audit, none of these rows
 /// are marked `isGap`, so the documented escalation-gap set is empty.
-@Suite("Manager Emissions: RileyLinkKit") struct RileyLinkKitAlertEmissionTests {
+@Suite("Trio Alert Emission: RileyLinkKit") struct RileyLinkKitAlertEmissionTests {
     private func id(_ manager: String, _ alertID: String) -> Alert.Identifier {
         Alert.Identifier(managerIdentifier: manager, alertIdentifier: alertID)
     }
@@ -160,7 +160,7 @@ import Testing
 /// Audit + classified data:
 /// loopkit-manager-synthesis/investigations/alert-notification-emissions/managers/pump/RileyLinkKit/
 /// Classifier source: Trio/Sources/Services/Alerts/TrioAlertCategory.swift
-@Suite("Manager Message Classification: RileyLinkKit") struct RileyLinkKitMessageClassificationTests {
+@Suite("Trio Alert Emission: RileyLinkKit — Classification") struct RileyLinkKitMessageClassificationTests {
     /// Stub whose `String(describing:)` IS the display string, so classification
     /// runs over the natural-language text a user would actually see.
     private struct StubError: Error, CustomStringConvertible {

TrioTests/TandemKitAlertEmissionTests.swift

@@ -48,7 +48,7 @@ import Testing
 /// input (a LoopKit `PumpManagerError` enum — not `CustomStringConvertible` —
 /// wrapping a `PumpCommError`/validation case) cannot be stated with
 /// certainty. Per the SCOPE rule those are omitted rather than guessed.
-@Suite("Manager Emissions: TandemKit") struct TandemKitAlertEmissionTests {
+@Suite("Trio Alert Emission: TandemKit") struct TandemKitAlertEmissionTests {
     /// TandemKit issues no LoopKit Alerts, so it carries no real
     /// `managerIdentifier`. We keep the audit's verbatim placeholder string so
     /// the (empty) registry-lookup pin documents exactly what was searched.
@@ -160,7 +160,7 @@ import Testing
 ///
 /// References: managers — TandemKit / TandemKitUI / TandemCore; pump —
 /// Tandem t:slim X2 / Mobi.
-@Suite("Message Classification: TandemKit") struct TandemKitMessageClassificationTests {
+@Suite("Trio Alert Emission: TandemKit — Classification") struct TandemKitMessageClassificationTests {
     /// A throwaway `Error` whose `String(describing:)` is exactly the emission
     /// display string, so `categorize(error:)` matches over natural-language
     /// text (mind the spaces: "reservoir is empty" does NOT contain