fix comments

Author: Radovan Fuchs

tests/e2e/features/unified-mode-migration.feature

@@ -17,15 +17,15 @@ Feature: Legacy to unified configuration migration
   Scenario: migrate then synthesize round-trips to the original run.yaml
      When lightspeed-stack --migrate-config is run for the legacy migration fixture pair
       And the active unified configuration is synthesized to run.yaml
-     Then the synthesized run.yaml is byte-identical to the legacy migration fixture run.yaml
+     Then the synthesized run.yaml parses to the same data as the legacy migration fixture run.yaml
 
 
   # --- library mode (@skip-in-server-mode) ---
 
   @skip-in-server-mode
   Scenario: Migrated unified configuration drives byte-identical Llama Stack behavior in library mode
-     When lightspeed-stack --migrate-config is run for the legacy migration fixture pair
-    Given The service uses the lightspeed-stack-unified-migrated.yaml configuration
+    Given lightspeed-stack --migrate-config is run for the legacy migration fixture pair
+      And The service uses the lightspeed-stack-unified-migrated.yaml configuration
       And The service is restarted
      When I access endpoint "readiness" using HTTP GET method
      Then The status code of the response is 200
@@ -40,8 +40,8 @@ Feature: Legacy to unified configuration migration
 
   @skip-in-library-mode
   Scenario: Migrated unified configuration drives byte-identical Llama Stack behavior in server mode
-     When lightspeed-stack --migrate-config is run for the legacy migration fixture pair
-    Given The service uses the lightspeed-stack-unified-migrated.yaml configuration
+    Given lightspeed-stack --migrate-config is run for the legacy migration fixture pair
+      And The service uses the lightspeed-stack-unified-migrated.yaml configuration
       And Llama Stack is restarted
       And Lightspeed Stack is restarted
      When I access endpoint "readiness" using HTTP GET method

tests/e2e/features/unified-mode-validation.feature

@@ -17,3 +17,9 @@ Feature: Unified mode configuration validation
     Given The service uses the lightspeed-stack-invalid-config-and-legacy.yaml configuration
      When configuration validation is attempted for the active configuration
      Then the validation error contains --migrate-config
+
+
+  Scenario: config_format_version legacy with unified-shaped body fails at load
+    Given The service uses the lightspeed-stack-invalid-version-legacy-unified-body.yaml configuration
+     When configuration validation is attempted for the active configuration
+     Then the validation error contains config_format_version