Merge pull request #2240 from asimurka/feature/rag-namespaces

LCORE-3186: Added namespaces to test RAG db

Author: tisnik

tests/e2e/features/llama_stack_disrupted.feature

@@ -61,17 +61,6 @@ Feature: Llama Stack connection disrupted
        {"detail": {"response": "Unable to connect to OGX", "cause": "Connection error."}}
     """
 
-  Scenario: Check if shields endpoint reports error when llama-stack is unreachable
-    Given The service uses the lightspeed-stack.yaml configuration
-      And The service is restarted
-    And The llama-stack connection is disrupted
-    When I access REST API endpoint "shields" using HTTP GET method
-    Then The status code of the response is 503
-    And The body of the response is the following
-    """
-       {"detail": {"response": "Unable to connect to OGX", "cause": "Connection error."}}
-    """
-
   Scenario: Check if tools endpoint reports error when llama-stack is unreachable
     Given The service uses the lightspeed-stack.yaml configuration
       And The service is restarted

tests/e2e/rag/README.md

@@ -2,6 +2,22 @@
 
 This directory holds committed BYOK vector stores used by the e2e suite.
 
+## OGX 1.0 KV key namespace
+
+OGX 1.0 FAISS persistence uses
+`persistence.namespace: vector_io::faiss` (see `run-ci.yaml` and LCS BYOK
+enrichment). SQLite KV keys are therefore stored as:
+
+```text
+vector_io::faiss:vector_stores:v3::<vector_store_id>
+vector_io::faiss:faiss_index:v3::<vector_store_id>
+…
+```
+
+Fixtures committed here must use that prefix. Pre-1.0 un-namespaced keys
+(`vector_stores:v3::…`) are invisible to OGX 1.0 and yield empty search
+results even when file_search / `vector_io.query` run successfully.
+
 ## `kv_store.db`
 
 Faiss BYOK store used by `faiss.feature` and `inline_rag.feature` (the