Add 'no integrations found' symptom to troubleshooting guide and FAQ entry

Author: Copilot

solutions/security/get-started/automatic-migration-troubleshooting.md

@@ -22,6 +22,7 @@ The `.kibana-siem-rule-migrations-integrations` index contains a `semantic_text`
 
 This causes the following symptoms:
 
+- **No integrations found for translated rules** — after completing an automatic migration, the **Integrations** column on the Translated rules page shows no integrations even when they should exist, because integration matching relies on semantic search against this index.
 - **Inconsistent search results across machines or clusters** — the same query returns different documents because the query-time inference model doesn't match the index-time model on the other cluster.
 - **Semantic search returning no results or wrong results** — Jina produces dense vectors; ELSER produces sparse vectors; they are incompatible vector spaces.
 - **`function_score` queries with `min_score` returning zero hits** — scores computed against mismatched embeddings are meaningless and rarely cross any threshold.

solutions/security/get-started/automatic-migration.md

@@ -271,6 +271,6 @@ Rule migration data appears in `.kibana-siem-rule-migrations-rules-default`. Das
 
 Assets that fall into this category will typically appear with a status of partially translated. You can use the [`LOOKUP JOIN`](elasticsearch://reference/query-languages/esql/esql-lookup-join.md) capability to help in this situation.
 
-**Why does semantic search return incorrect or inconsistent results after migration?**
+**Why does semantic search return incorrect or inconsistent results after migration, or why are no integrations shown for translated rules?**
 
-This can occur if the `.kibana-siem-rule-migrations-integrations` index was created when the ELSER inference endpoint was unavailable, causing it to fall back to a different embedding model. Refer to [Troubleshoot Automatic Migration](automatic-migration-troubleshooting.md) for instructions on how to re-create the index with the correct ELSER inference endpoint.
+This can occur if the `.kibana-siem-rule-migrations-integrations` index was created when the ELSER inference endpoint was unavailable, causing it to fall back to a different embedding model. This mismatched model causes integration matching to fail, resulting in no integrations appearing for translated rules, as well as inconsistent or empty semantic search results. Refer to [Troubleshoot Automatic Migration](automatic-migration-troubleshooting.md) for instructions on how to re-create the index with the correct ELSER inference endpoint.