[uss_quafilier] Lower severity of cleanup no to have 'high' during cleanup phase (#1404)

the-glu · web-flow · commit a1708135412f · 2026-04-06T10:28:41.000-07:00
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/isa_simple.md
@@ -212,11 +212,11 @@ The ISA search are parameter cover the resource ISA, but it has been previously
 
 The cleanup phase of this test scenario attempts to remove the ISA if the test ended prematurely.
 
-### 🛑 Successful ISA query check
+### ⚠️ Successful ISA query check
 
 **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** requires the implementation of the DSS endpoint enabling retrieval of information about a specific ISA; if the individual ISA cannot be retrieved and the error isn't a 404, then this requirement isn't met.
 
-### 🛑 Removed pre-existing ISA check
+### ⚠️ Removed pre-existing ISA check
 
 If an ISA with the intended ID is still present in the DSS, it needs to be removed before exiting the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met.
 
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_simple.md
@@ -387,11 +387,11 @@ If the DSS returns the deleted subscription in a search that covers the area it
 
 The cleanup phase of this test scenario removes the subscription with the known test ID if it has not been removed before.
 
-#### 🛑 Subscription can be queried by ID check
+#### ⚠️ Subscription can be queried by ID check
 
 If the DSS cannot be queried for the existing test ID, the DSS is likely not implementing **[astm.f3411.v19.DSS0030,e](../../../../../requirements/astm/f3411/v19.md)** correctly.
 
-#### 🛑 Subscription can be deleted check
+#### ⚠️ Subscription can be deleted check
 
 An attempt to delete a subscription when the correct version is provided should succeed, otherwise the DSS is in violation of **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)**.
 
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/subscription_validation.md
@@ -93,10 +93,10 @@ The ability to delete an existing subscription is required in **[astm.f3411.v19.
 
 The cleanup phase of this test scenario will remove any subscription that may have been created during the test and that intersects with the test ISA.
 
-### 🛑 Successful subscription search query check
+### ⚠️ Successful subscription search query check
 
 If the query for subscriptions fails, the "GET Subscriptions" portion of **[astm.f3411.v19.DSS0030,f](../../../../../requirements/astm/f3411/v19.md)** was not met.
 
-### 🛑 Subscription can be deleted check
+### ⚠️ Subscription can be deleted check
 
 If the deletion attempt fails, the "DELETE Subscription" portion of **[astm.f3411.v19.DSS0030,d](../../../../../requirements/astm/f3411/v19.md)** was not met.
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v19/dss/token_validation.md
@@ -107,11 +107,11 @@ When an ISA is deleted, subscribers must be notified. If a subscriber cannot be
 
 The cleanup phase of this test scenario attempts to remove the ISA if the test ended prematurely.
 
-### 🛑 Successful ISA query check
+### ⚠️ Successful ISA query check
 
 **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** requires the implementation of the DSS endpoint enabling retrieval of information about a specific ISA; if the individual ISA cannot be retrieved and the error isn't a 404, then this requirement isn't met.
 
-### 🛑 Removed pre-existing ISA check
+### ⚠️ Removed pre-existing ISA check
 
 If an ISA with the intended ID is still present in the DSS, it needs to be removed before exiting the test. If that ISA cannot be deleted, then the **[astm.f3411.v19.DSS0030,b](../../../../../requirements/astm/f3411/v19.md)** requirement to implement the ISA deletion endpoint might not be met.
 
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/isa_simple.md
@@ -212,11 +212,11 @@ The ISA search are parameter cover the resource ISA, but it has been previously
 
 The cleanup phase of this test scenario attempts to remove the ISA if the test ended prematurely.
 
-### 🛑 Successful ISA query check
+### ⚠️ Successful ISA query check
 
 **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** requires the implementation of the DSS endpoint enabling retrieval of information about a specific ISA; if the individual ISA cannot be retrieved and the error isn't a 404, then this requirement isn't met.
 
-### 🛑 Removed pre-existing ISA check
+### ⚠️ Removed pre-existing ISA check
 
 If an ISA with the intended ID is still present in the DSS, it needs to be removed before exiting the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met.
 
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_simple.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_simple.md
@@ -380,10 +380,10 @@ If the DSS returns the deleted subscription in a search that covers the area it
 
 The cleanup phase of this test scenario removes the subscription with the known test ID if it has not been removed before.
 
-#### 🛑 Subscription can be queried by ID check
+#### ⚠️ Subscription can be queried by ID check
 
 If the DSS cannot be queried for the existing test ID, the DSS is likely not implementing **[astm.f3411.v22a.DSS0030,e](../../../../../requirements/astm/f3411/v22a.md)** correctly.
 
-#### 🛑 Subscription can be deleted check
+#### ⚠️ Subscription can be deleted check
 
 An attempt to delete a subscription when the correct version is provided should succeed, otherwise the DSS is in violation of **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)**.
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/subscription_validation.md
@@ -93,10 +93,10 @@ The ability to delete an existing subscription is required in **[astm.f3411.v22a
 
 The cleanup phase of this test scenario will remove any subscription that may have been created during the test and that intersects with the test ISA.
 
-### 🛑 Successful subscription search query check
+### ⚠️ Successful subscription search query check
 
 If the query for subscriptions fails, the "GET Subscriptions" portion of **[astm.f3411.v22a.DSS0030,f](../../../../../requirements/astm/f3411/v22a.md)** was not met.
 
-### 🛑 Subscription can be deleted check
+### ⚠️ Subscription can be deleted check
 
 If the deletion attempt fails, the "DELETE Subscription" portion of **[astm.f3411.v22a.DSS0030,d](../../../../../requirements/astm/f3411/v22a.md)** was not met.
diff --git a/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md b/monitoring/uss_qualifier/scenarios/astm/netrid/v22a/dss/token_validation.md
@@ -107,11 +107,11 @@ When an ISA is deleted, subscribers must be notified. If a subscriber cannot be
 
 The cleanup phase of this test scenario attempts to remove the ISA if the test ended prematurely.
 
-### 🛑 Successful ISA query check
+### ⚠️ Successful ISA query check
 
 **[interuss.f3411.dss_endpoints.GetISA](../../../../../requirements/interuss/f3411/dss_endpoints.md)** requires the implementation of the DSS endpoint enabling retrieval of information about a specific ISA; if the individual ISA cannot be retrieved and the error isn't a 404, then this requirement isn't met.
 
-### 🛑 Removed pre-existing ISA check
+### ⚠️ Removed pre-existing ISA check
 
 If an ISA with the intended ID is still present in the DSS, it needs to be removed before exiting the test. If that ISA cannot be deleted, then the **[astm.f3411.v22a.DSS0030,b](../../../../../requirements/astm/f3411/v22a.md)** requirement to implement the ISA deletion endpoint might not be met.
 
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/get_op_data_validation.md b/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/get_op_data_validation.md
@@ -98,6 +98,7 @@ direct retrieval by tested_uss from mock_uss.
 Teardown
 
 ## Cleanup
+
 ### ⚠️ Successful flight deletion check
 This cleanup is for both - after testcase ends and after test scenario ends
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../requirements/interuss/automated_testing/flight_planning.md)**
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/flight_intent_validation/flight_intent_validation.md b/monitoring/uss_qualifier/scenarios/astm/utm/flight_intent_validation/flight_intent_validation.md
@@ -141,5 +141,6 @@ to reject or accept the flight. If the USS indicates that the attempt failed, th
 #### [Validate Tiny Overlap Conflict Flight not planned](../validate_not_shared_operational_intent.md)
 
 ## Cleanup
+
 ### ⚠️ Successful flight deletion check
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../requirements/interuss/automated_testing/flight_planning.md)**
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/nominal_planning/conflict_equal_priority_not_permitted/conflict_equal_priority_not_permitted.md b/monitoring/uss_qualifier/scenarios/astm/utm/nominal_planning/conflict_equal_priority_not_permitted/conflict_equal_priority_not_permitted.md
@@ -277,5 +277,6 @@ This step validates that the response of the USS is consistent with the flight s
 modification, i.e. whether Flight 1 was not modified.
 
 ## Cleanup
+
 ### ⚠️ Successful flight deletion check
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../../requirements/interuss/automated_testing/flight_planning.md)**
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/nominal_planning/conflict_higher_priority/conflict_higher_priority.md b/monitoring/uss_qualifier/scenarios/astm/utm/nominal_planning/conflict_higher_priority/conflict_higher_priority.md
@@ -286,5 +286,6 @@ In addition, Flight 1 should not have been removed, because doing so would leave
 Because the modification attempt was invalid, Flight 1 should not have been modified.
 
 ## Cleanup
+
 ### ⚠️ Successful flight deletion check
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../../requirements/interuss/automated_testing/flight_planning.md)**
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/off_nominal_planning/down_uss.md b/monitoring/uss_qualifier/scenarios/astm/utm/off_nominal_planning/down_uss.md
@@ -117,10 +117,10 @@ If the planning was rejected, Flight 1 should not have been shared, thus should
 ## Cleanup
 ### [Restore virtual USS availability test step](../set_uss_available.md)
 
-### 🛑 Successful flight deletion check
+### ⚠️ Successful flight deletion check
 Delete flights injected at USS through the flight planning interface.
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../requirements/interuss/automated_testing/flight_planning.md)**
 
-### 🛑 Successful operational intents cleanup check
+### ⚠️ Successful operational intents cleanup check
 Delete operational intents created at DSS by virtual USS.
 If the search for operational intent references or their deletion fail, this check fails per **[astm.f3548.v21.DSS0005,2](../../../../requirements/astm/f3548/v21.md)** or **[astm.f3548.v21.DSS0005,1](../../../../requirements/astm/f3548/v21.md)**, respectively.
diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/off_nominal_planning/down_uss_equal_priority_not_permitted.md b/monitoring/uss_qualifier/scenarios/astm/utm/off_nominal_planning/down_uss_equal_priority_not_permitted.md
@@ -175,10 +175,10 @@ to reject or accept Flight 2. If the USS indicates that the injection attempt fa
 ## Cleanup
 ### [Restore virtual USS availability test step](../set_uss_available.md)
 
-### 🛑 Successful flight deletion check
+### ⚠️ Successful flight deletion check
 Delete flights injected at USS through the flight planning interface.
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../../requirements/interuss/automated_testing/flight_planning.md)**
 
-### 🛑 Successful operational intents cleanup check
+### ⚠️ Successful operational intents cleanup check
 Delete operational intents created at DSS by virtual USS.
 If the search for operational intent references or their deletion fail, this check fails per **[astm.f3548.v21.DSS0005,2](../../../../requirements/astm/f3548/v21.md)** or **[astm.f3548.v21.DSS0005,1](../../../../requirements/astm/f3548/v21.md)**, respectively.
diff --git a/monitoring/uss_qualifier/scenarios/uspace/flight_auth/validation.md b/monitoring/uss_qualifier/scenarios/uspace/flight_auth/validation.md
@@ -66,6 +66,6 @@ uss_qualifier indicates to the flight planner a user intent to create a valid fl
 
 ## Cleanup
 
-### 🛑 Successful flight deletion check
+### ⚠️ Successful flight deletion check
 
 **[interuss.automated_testing.flight_planning.DeleteFlightSuccess](../../../requirements/interuss/automated_testing/flight_planning.md)**
