Merge remote-tracking branch 'origin/main' into virtual_threads

# Conflicts:
#	server/src/main/java/org/elasticsearch/TransportVersions.java

Author: nicktindall

docs/changelog/131341.yaml

@@ -0,0 +1,5 @@
+pr: 131341
+summary: Consider min/max from predicates when transform date_trunc/bucket to `round_to`
+area: ES|QL
+type: enhancement
+issues: []

docs/changelog/131536.yaml

@@ -1,5 +1,5 @@
 pr: 131536
-summary: "Component Templates: Add `{created,modified}_date`"
+summary: "Component Templates: Add created and modified date"
 area: Ingest Node
 type: enhancement
 issues: []

docs/changelog/132083.yaml

@@ -0,0 +1,5 @@
+pr: 132083
+summary: "Index template: Add created_date and modified_date"
+area: Ingest Node
+type: enhancement
+issues: []

docs/changelog/132143.yaml

@@ -0,0 +1,6 @@
+pr: 132143
+summary: Consider min/max from predicates when transform date_trunc/bucket to `round_to`
+  option 2
+area: ES|QL
+type: enhancement
+issues: []

docs/changelog/132459.yaml

@@ -0,0 +1,5 @@
+pr: 132459
+summary: Small fixes for COPY_SIGN
+area: ES|QL
+type: bug
+issues: []

docs/changelog/132511.yaml

@@ -0,0 +1,5 @@
+pr: 132511
+summary: Handle special regex cases for version fields
+area: Search
+type: bug
+issues: []

docs/reference/elasticsearch/mapping-reference/semantic-text.md

@@ -486,6 +486,29 @@ PUT test-index
 }
 ```
 
+## Troubleshooting semantic_text fields [troubleshooting-semantic-text-fields]
+
+If you want to verify that your embeddings look correct, you can view the
+inference data that `semantic_text` typically hides using `fields`.
+
+```console
+POST test-index/_search
+{
+    "query": {
+        "match": {
+            "my_semantic_field": "Which country is Paris in?"
+        },
+        "fields": [
+            "_inference_fields"
+          ]
+    }
+}
+```
+
+This will return verbose chunked embeddings content that is used to perform
+semantic search for `semantic_text` fields.
+
+
 ## Limitations [limitations]
 
 `semantic_text` field types have the following limitations: