Merge branch 'main' into lucabelluccini-patch-1

Author: theletterf

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+<!--
+Thank you for contributing to the Elastic Docs! 🎉
+Use this template to help us efficiently review your contribution.
+-->
+
+## Summary
+<!--
+Describe what your PR changes or improves.  
+If your PR fixes an issue, link it here. If your PR does not fix an issue, describe the reason you are making the change. 
+-->
+
+## Generative AI disclosure
+<!--
+To help us ensure compliance with the Elastic open source and documentation guidelines, please answer the following:
+-->
+1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
+- [ ] Yes  
+- [ ] No  
+<!--
+2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).
+
+Tool(s) and model(s) used:
+-->
+

.github/workflows/vale-linting.yml

@@ -0,0 +1,22 @@
+name: Vale Documentation Linting
+
+on:
+  pull_request:
+    paths:
+      - '**.md'
+      - '**.adoc'
+
+permissions:
+  contents: read
+
+jobs:
+  vale:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+      
+      - name: Run Vale Linter
+        uses: elastic/vale-rules/lint@main

.github/workflows/vale-reporting.yml

@@ -0,0 +1,23 @@
+name: Vale Report
+
+on:
+  workflow_run:
+    workflows: ["Vale Documentation Linting"]
+    types:
+      - completed
+
+permissions:
+  pull-requests: read
+
+jobs:
+  report:
+    runs-on: ubuntu-latest
+    if: github.event.workflow_run.event == 'pull_request'
+    permissions:
+      pull-requests: write
+    
+    steps:
+      - name: Post Vale Results
+        uses: elastic/vale-rules/report@main
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}

contribute-docs/api-docs/kibana-api-docs-quickstart.md

@@ -202,7 +202,7 @@ responses:
 :sync: code-generated
 
 :::{note}
-**This step is optional.** CI will automatically capture the snapshot when you push your `.ts` changes. Running this locally is useful for validating changes before pushing or debugging issues. See [`capture_oas_snapshot.sh`](https://github.com/elastic/kibana/blob/main/.buildkite/scripts/steps/checks/capture_oas_snapshot.sh) for the full list of paths captured in CI.
+**This step is optional.** CI will automatically capture the snapshot when you push your `.ts` changes. Running this locally is useful for validating changes before pushing or debugging issues.
 :::
 
 This step captures the OpenAPI specification that {{kib}} generates at runtime from your route definitions. It spins up a local {{es}} and {{kib}} cluster with your code changes. This generates the following output files in the `oas_docs` directory:
@@ -214,13 +214,27 @@ This step captures the OpenAPI specification that {{kib}} generates at runtime f
 - [Docker](https://docs.docker.com/get-docker/) must be running
 - If you're an Elastician, ensure you're logged into Docker with your Elastic account
 
-**Capture all API paths** (recommended):
+To capture all the documented API paths, copy the command from [`capture_oas_snapshot.sh`](https://github.com/elastic/kibana/blob/main/.buildkite/scripts/steps/checks/capture_oas_snapshot.sh). For example:
 
 ```bash
-node scripts/capture_oas_snapshot --update
+node scripts/capture_oas_snapshot \
+  --include-path /api/status \
+  --include-path /api/alerting/rule/ \
+  --include-path /api/alerting/rules \
+  --include-path /api/actions \
+  --include-path /api/security/role \
+  --include-path /api/spaces \
+  --include-path /api/streams \
+  --include-path /api/fleet \
+  --include-path /api/saved_objects/_import \
+  --include-path /api/saved_objects/_export \
+  --include-path /api/maintenance_window \
+  --include-path /api/agent_builder
+  --update
 ```
 
-**For faster iteration**, capture the specific paths you're working on:
+For faster iteration, you can capture the specific paths you're working on, though this minimized output should not be included in your pull request.
+For example:
 
 ```bash
 node scripts/capture_oas_snapshot --update --include-path /api/your/specific/path

deploy-manage/deploy/deployment-comparison.md

@@ -18,7 +18,7 @@ For more details about feature availability in Serverless, check [](elastic-clou
 
 | Feature/capability | Self-managed | {{ech}} | Serverless |
 |-------------------|-------------|--------------------------------|-------------------------|
-| Hosting | Any infrastructure | {{ecloud}} through AWS, Azure, or GCP | {{ecloud}} through AWS or Azure |
+| Hosting | Any infrastructure | {{ecloud}} through AWS, Azure, or GCP | {{ecloud}} through AWS, Azure, or GCP |
 | Hardware configuration | Full control | Limited control | Managed by Elastic |
 | Autoscaling | No | Available | Automatic |
 | Data tiers management | Through ILM policies | Available | No data tiers |

deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md

@@ -16,8 +16,9 @@ products:
 
 To complete this tutorial, you need:
 
-* The `manage` cluster privilege on the local cluster.
-* A license on both clusters that includes {{ccr}}. [Activate a free 30-day trial](../../license/manage-your-license-in-self-managed-cluster.md).
-* An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana).
-* In the local cluster, all nodes with the `master` [node role](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md#node-roles) must also have the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. The local cluster must also have at least one node with both a data role and the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. Individual tasks for coordinating replication scale based on the number of data nodes with the `remote_cluster_client` role in the local cluster.
+- The `manage` cluster privilege on the local cluster.
+- Both clusters must have the same [license](/deploy-manage/license.md) type, and that license must support {{ccr}}.
+  - [Activate a free 30-day trial](../../license/manage-your-license-in-self-managed-cluster.md).
+- An index on the remote cluster that contains the data you want to replicate. This tutorial uses the sample eCommerce orders data set. [Load sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana).
+- In the local cluster, all nodes with the `master` [node role](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md#node-roles) must also have the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. The local cluster must also have at least one node with both a data role and the [`remote_cluster_client`](../../distributed-architecture/clusters-nodes-shards/node-roles.md#remote-node) role. Individual tasks for coordinating replication scale based on the number of data nodes with the `remote_cluster_client` role in the local cluster.
 

manage-data/data-store/data-streams/set-up-tsds.md

@@ -63,7 +63,6 @@ PUT _ilm/policy/my-weather-sensor-lifecycle-policy
         }
       }
       // Additional phases (warm, cold, delete) as needed
-      }
     }
   }
 }
@@ -85,10 +84,10 @@ The structure of a time series data stream is defined by an index template. Crea
         - To define dimensions dynamically, you can use a pass-through object. For details, refer to [Defining sub-fields as time series dimensions](elasticsearch://reference/elasticsearch/mapping-reference/passthrough.md#passthrough-dimensions).
     - **Metrics:** To define a metric, use the `time_series_metric` mapping parameter. For details, refer to [Metrics](/manage-data/data-store/data-streams/time-series-data-stream-tsds.md#time-series-metric).
     - **Timestamp** (optional): Define a `date` or `date_nanos` mapping for the `@timestamp` field. If you don't specify a mapping, {{es}} maps `@timestamp` as a `date` field with default options.
-    -  {applies_to}`serverless: unavailable` {applies_to}`stack: ga` **Lifecycle management**: For {{stack}}, include lifecycle settings to enable automatic rollover and prevent indices from growing too large. 
-        - Set `"lifecycle": { "enabled": true }`. 
-        - If you created an ILM policy in [step 1](#tsds-ilm-policy), reference it with `index.lifecycle.name`.
-    - **Other settings**  (optional): Additional index settings, such as [`index.number_of_replicas`](elasticsearch://reference/elasticsearch/index-settings/index-modules.md#dynamic-index-number-of-replicas), for the data stream's backing indices.
+    - {applies_to}`serverless: unavailable` {applies_to}`stack: ga` **Lifecycle management**: If you're using {{stack}}, define a lifecycle to enable automatic rollover and prevent indices from growing too large.
+        - Add a `lifecycle` object and specify `"enabled": true`. 
+        - If you created an ILM policy in [step 1](#tsds-ilm-policy), reference it in the settings with `index.lifecycle.name`.
+    - **Settings** (optional): Define any relevant index settings, such as [`index.number_of_replicas`](elasticsearch://reference/elasticsearch/index-settings/index-modules.md#dynamic-index-number-of-replicas), for the data stream's backing indices.
 - **Priority:** Set the priority higher than `200` to avoid [collisions](/manage-data/data-store/templates.md#avoid-index-pattern-collisions) with built-in templates.
 
 **Example index template PUT request:**
@@ -101,10 +100,10 @@ PUT _index_template/my-weather-sensor-index-template
   "template": {
     "settings": {
       "index.mode": "time_series",
-      "index.lifecycle.name": "my-lifecycle-policy", <1>
-      "lifecycle": { 
-        "enabled": true <2>
-      }
+      "index.lifecycle.name": "my-lifecycle-policy" <1>
+    },
+    "lifecycle": { 
+      "enabled": true <2>
     },
     "mappings": {
       "properties": {

reference/fleet/data-streams-scenario3.md

@@ -56,13 +56,13 @@ metrics-system.network-production@custom
 3. Use the template above to set the name—in this case, `metrics-system.network-production@custom`. Click **Next**.
 4. Under **Index settings**, set the {{ilm-init}} policy name under the `lifecycle.name` key:
 
-    ```json
-    {
-      "lifecycle": {
-        "name": "90-days-default"
-      }
-    }
-    ```
+   ```json
+   {
+     "lifecycle": {
+       "name": "90-days-default"
+     }
+   }
+   ```
 
 5. Continue to **Review** and ensure your request looks similar to the image below. If it does, click **Create component template**.
 
@@ -78,10 +78,9 @@ metrics-system.network-production@custom
 Now that you’ve created a component template, you need to create an index template to apply the changes to the correct data stream. The easiest way to do this is to duplicate and modify the integration’s existing index template.
 
 ::::{warning}
-- If you duplicate an index template, do not change or remove any managed properties. This may result in problems when upgrading. Cloning the index template of an integration package involves some risk as any changes made to the original index template are not propagated to the cloned version when you upgrade versions. 
-- These steps assume that you want to have a namespace specific ILM policy, which requires index template cloning. Cloning the index template of an integration package involves some risk because any changes made to the original index template as part of package upgrades are not propagated to the cloned version. Check out [Cloning the index template of an integration package](/reference/fleet/integrations-assets-best-practices.md#assets-restrictions-cloning-index-template) for details.
-
-+ If you want to change the ILM Policy, the number of shards, or other settings for the datastreams of one or more integrations, but **the changes do not need to be specific to a given namespace**, use a `@custom` component template, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md), to avoid the problems mentioned earlier. Check out the [ILM](/reference/fleet/data-streams.md#data-streams-ilm) section for details.
+* If you duplicate an index template, do not change or remove any managed properties. This may result in problems when upgrading. Cloning the index template of an integration package involves some risk as any changes made to the original index template are not propagated to the cloned version when you upgrade versions. 
+* These steps assume that you want to have a namespace specific ILM policy, which requires index template cloning. Cloning the index template of an integration package involves some risk because any changes made to the original index template as part of package upgrades are not propagated to the cloned version. Check out [Cloning the index template of an integration package](/reference/fleet/integrations-assets-best-practices.md#assets-restrictions-cloning-index-template) for details.
+* If you want to change the ILM policy, the number of shards, or other settings for the data streams of one or more integrations, but **the changes do not need to be specific to a given namespace**, use a `@custom` component template, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md), to avoid the problems mentioned earlier. Check out the [ILM](/reference/fleet/data-streams.md#data-streams-ilm) section for details.
 
 ::::
 

solutions/search/agent-builder/limitations-known-issues.md

@@ -40,6 +40,8 @@ Error: Invalid function call syntax
 Error executing agent: No tool calls found in the response.
 ```
 
+$$$conversation-length-exceeded$$$
+
 ### {{esql}} limitations
 
 {{esql}} tools are subject to the current limitations of the {{esql}} language itself. For example, [named parameters](elasticsearch://reference/query-languages/esql/esql-syntax.md#esql-function-named-params) (`?parameter_name`) do not currently work with the `LIKE` and `RLIKE` operators ([issue #131356](https://github.com/elastic/elasticsearch/issues/131356)).