updating the requirement Ids based on the new feature requirements

Author: Saumya-R

feature_integration_tests/test_cases/BUILD

@@ -188,9 +188,8 @@ score_py_pytest(
     deps = all_requirements,
 )
 
-# Dedicated, isolated coverage for ready_recovery_action.restart.number_of_attempts
-# (feat_req__lifecycle__retries_configurable). Each daemon invocation generates its own
-# single-component config and runtime tree under TEST_TMPDIR.
+# Dedicated, isolated coverage for ready_recovery_action.restart.number_of_attempts. Each daemon
+# invocation generates its own single-component config and runtime tree under TEST_TMPDIR.
 score_py_pytest(
     name = "fit_lifecycle_retries",
     timeout = "long",

feature_integration_tests/test_cases/tests/lifecycle/test_conditional_launching.py

@@ -58,10 +58,8 @@ class TestConditionalLaunchingBlocksOnMissingDependency:
 
     @add_test_properties(
         partially_verifies=[
-            "feat_req__lifecycle__waitfor_support",
-            "feat_req__lifecycle__dependency_check",
+            "feat_req__lifecycle__conditional_startup",
             "feat_req__lifecycle__process_ordering",
-            "feat_req__lifecycle__define_swc_dependencies",
         ],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
@@ -73,8 +71,8 @@ def test_rust_stays_down_until_cpp_dependency_becomes_available(
         launch failure at least twice (it keeps retrying rather than aborting). After cpp is made
         executable, cpp and then rust must be running within 8 s each.
 
-        Limitations: "running" is pgrep process existence; rust has a single dependency, so
-        `dependency_check` ("all dependencies") cannot be told apart from "any dependency".
+        Limitations: "running" is pgrep process existence; rust has a single dependency, so this
+        does not distinguish single-edge gating from multi-dependency behavior.
         No `cond_process_start` claim: that requirement is about starting on the return value
         of earlier processes, which this config does not use.
         """

feature_integration_tests/test_cases/tests/lifecycle/test_process_launching_with_daemon.py

@@ -148,7 +148,7 @@ def test_startup_declares_and_launches_multiple_processes(
         assert daemon.is_running(), "Launch Manager daemon stopped unexpectedly"
 
     @add_test_properties(
-        partially_verifies=["feat_req__lifecycle__process_launch_args"],
+        partially_verifies=["feat_req__lifecycle__launch_support"],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
     )
@@ -182,7 +182,7 @@ def test_launch_process_arguments_are_applied(
             )
 
     @add_test_properties(
-        partially_verifies=["feat_req__lifecycle__process_launch_args"],
+        partially_verifies=["feat_req__lifecycle__launch_support"],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
     )
@@ -214,7 +214,7 @@ def test_launch_process_environment_is_applied(
                 f"{key} mismatch for {app_name}: expected {expected_value!r}, got {proc_env.get(key)!r}"
             )
 
-    # No requirement claim (feat_req__lifecycle__uid_gid_support): skips in CI, which neither sets
+    # No requirement claim: skips in CI, which neither sets
     # FIT_ENABLE_SETCAP=1 nor runs unsandboxed, both needed for the setcap grant. See README.md.
     def test_launched_process_uid_gid_matches_config_when_applied(
         self,
@@ -371,7 +371,7 @@ def test_scheduling_policy_is_non_default_and_applied(
         )
 
     @add_test_properties(
-        partially_verifies=["feat_req__lifecycle__secpol_non_root"],
+        partially_verifies=["feat_req__lifecycle__launch_support"],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
     )

feature_integration_tests/test_cases/tests/lifecycle/test_retry_exhaustion.py

@@ -19,8 +19,8 @@
 - `TestRetryExhaustionTriggersRecovery`: the app always crashes; the daemon must stop after
   1 + `number_of_attempts` launches and stay alive.
 
-Limitation for `retries_configurable`: only the single configured value (2) is exercised; the
-count is not varied across runs.
+Limitation: only the single configured retry value (2) is exercised; the count is not varied
+across runs.
 """
 
 from __future__ import annotations
@@ -51,7 +51,7 @@ class TestRetrySucceedsWithinConfiguredAttempts(RetryDaemonScenario):
     crashes_before_success = 2
 
     @add_test_properties(
-        partially_verifies=["feat_req__lifecycle__retries_configurable"],
+        partially_verifies=["feat_req__lifecycle__launch_support"],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
     )
@@ -88,7 +88,7 @@ class TestRetryExhaustionTriggersRecovery(RetryDaemonScenario):
     crashes_before_success = 999
 
     @add_test_properties(
-        partially_verifies=["feat_req__lifecycle__retries_configurable"],
+        partially_verifies=["feat_req__lifecycle__launch_support"],
         test_type="requirements-based",
         derivation_technique="requirements-analysis",
     )