Merge branch 'main' into 11-custom-roles-remove-conditions

Author: joepeeples

.github/ISSUE_TEMPLATE/breaking-change.yaml

@@ -0,0 +1,40 @@
+name: "Breaking change report"
+description: "Report a breaking change in Elastic Security"
+title: "[BREAKING CHANGE] "
+labels: "breaking-change"
+body: 
+  - type: markdown
+    attributes:
+      value: |
+        Hello! Use this form to report a breaking change in Elastic Security software to the [@elastic/security-docs](https://github.com/orgs/elastic/teams/security-docs) team. We will add it to the release notes for the version that introduces the breaking change.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What feature will break? Any more details about how it will break? Please include any recommendations for users who were using the feature with the breaking change.
+    validations:
+      required: true
+  - type: dropdown
+    id: doc-set
+    attributes:
+      label: Which deployment types are affected?
+      description: ESS (classic), serverless, or both?
+      options:
+        - ESS and serverless
+        - ESS only
+        - Serverless only
+        - Unknown
+      default: 0
+    validations:
+      required: true
+  - type: textarea
+    id: software-version
+    attributes:
+      label: Release version
+      description: If you selected ESS above, please list which Stack version(s) this breaking change applies to. 
+      placeholder: |
+        For example:
+        "This breaking change applies to Stack versions 8.10 and newer." 
+         "N/A"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/docs-request-internal.yaml

@@ -1,5 +1,5 @@
-name: "Internal documentation request (Elastic employees) "
-description: Request a documentation change or enhancement. For tasks you don't want exposed to the public, create an issue in [elastic/security-docs-internal](https://github.com/elastic/security-docs-internal).
+name: "Doc request for a new feature or enhancement (Elastic employees only)"
+description: Request documentation for a new feature or enhancement.
 title: "[Request] "
 body:
   - type: markdown

.github/ISSUE_TEMPLATE/enhancement-request.yaml

@@ -1,17 +1,17 @@
-name: "Security docs enhancement request"
-description: Submit an issue to request an improvement to Elastic Security documentation.
-title: "[Enhancement]: "
-labels: "enhancement"
+name: "Request a documentation improvement"
+description: Request a change to improve Elastic Security docs.
+title: "[Suggestion] "
+labels: "suggestion"
 body:
   - type: markdown
     attributes:
       value: |
-        Hello! Use this form to submit an enhancement request to the [@elastic/security-docs](https://github.com/orgs/elastic/teams/security-docs) team. 
+        Hello! Do you see something in our docs that needs clarification, more info, or something else we can improve? Use this form to submit a request to our [@elastic/security-docs](https://github.com/orgs/elastic/teams/security-docs) team. 
   - type: textarea
     id: description
     attributes:
-      label: Description
-      description: Summarize your request here. What is the problem?
+      label: What can we change to make the docs better? 
+      description: Please describe what the issue is and what we can do to improve it.  
       placeholder: |
         What: We need documentation for X.
         Why: We've received support requests that indicate customers are struggling with Y in versions A and B. 
@@ -20,15 +20,12 @@ body:
   - type: textarea
     id: related
     attributes:
-      label: Related links / assets
+      label: Doc URL
       description: How can we learn more about the problem?
       value: |
-        Please include each of the following, if applicable:
+        Please include the doc URL and any other related information where applicable:
         Doc URL: 
-        Subject matter expert:
-        Figma link(s):
-        Github epic link(s):
-        Github issue link(s):
+        Github issue link(s)/Other resources:
     validations:
       required: false
   - type: dropdown
@@ -55,28 +52,7 @@ body:
         "The docs are good after version 8.10, but need updating in 8.7, 8.8, and 8.9"
     validations:
       required: true
-  - type: textarea
-    id: collaborators
-    attributes:
-      label: Collaborators
-      description: If applicable, please include contact information for the relevant product manager, designer, and developer.
-      value: |
-        PM:
-        Designer: 
-        Developer:
-        Others (if applicable):
-    validations:
-      required: false
-  - type: textarea
-    id: timeline
-    attributes:
-      label: Timeline / deliverables
-      description: When would it be ideal for for us to complete the request?
-      placeholder: |
-        Please provide any information that would help us prioritize this request.
-    validations:
-      required: true
   - type: markdown
     attributes:
       value: |
-        Thanks for submitting this issue! For urgent issues, we encourage you to send a message in the [#security-docs](https://elastic.slack.com/archives/C013W8WME2Z) Slack channel.
+        Thanks for submitting this issue! For urgent issues, we encourage you to send a message in the [#security-docs](https://elastic.slack.com/archives/C013W8WME2Z) Slack channel.

.github/ISSUE_TEMPLATE/issue.md

@@ -9,13 +9,18 @@ Documentation Manager: Janeen Roberts (Github: `@jmikell821`)
 
 ## Contributing to Elastic Security docs
 
-If you're an Elastic employee, you can open an issue using the appropriate [template](https://github.com/elastic/security-docs/issues/new/choose). To contribute directly to Elastic Security documentation:
+You can open an issue using the appropriate [template](https://github.com/elastic/security-docs/issues/new/choose). 
+
+> [!NOTE]
+> Please report any **known issues** that need to be documented by creating an issue in our [private repo](https://github.com/elastic/security-docs-internal/issues) using the known issue template. 
+
+To contribute directly to Elastic Security documentation:
 
 1. Please fork and clone the `security-docs` repo. 
 1. Check out the `main` branch and fetch the latest changes. 
 1. Check out a new branch and make your changes. 
 1. Save your changes and open a pull request. 
-1. Add the [@elastic/security-docs](https://github.com/orgs/elastic/teams/security-docs) team and any other appropriate members as reviewers. 
+1. Add all appropriate Github users as reviewers.  
 1. Add the appropriate release version label, backport version label if appropriate, and team label to the PR. 
 1. If your PR changes any [serverless docs content](https://github.com/elastic/security-docs/tree/main/docs/serverless), add the label `ci:doc-build` to generate a preview of the serverless docs on the PR.
 1. Once the docs team approves all changes, you can merge it. If a backport version label was added to a PR for stack versions 7.14.0 and newer, mergify will automatically open a backport PR. 

README.md

@@ -1,6 +1,12 @@
 [[anonymization-fields-api-find]]
 === Find anonymization fields
 
+.New API Reference
+[sidebar]
+--
+For the most up-to-date API details, refer to {api-kibana}/group/endpoint-security-ai-assistant-api[AI Assistant APIs].
+--
+
 Retrieve a list of anonymization fields that can be included in the LLM context.
 
 [discrete]

docs/AI-for-security/api/anonymization-fields-api-find.asciidoc

@@ -2,4 +2,10 @@
 [role="xpack"]
 == Elastic AI Assistant API
 
+.New API Reference
+[sidebar]
+--
+For the most up-to-date API details, refer to {api-kibana}/group/endpoint-security-ai-assistant-api[AI Assistant APIs].
+--
+
 The Elastic AI Assistant API allows you to interact with and manage Elastic AI Assistant.

docs/AI-for-security/api/assistant-api-overview.asciidoc

@@ -1,6 +1,12 @@
 [[bulk-actions-anonymization-fields-api]]
 === Bulk anonymization field actions
 
+.New API Reference
+[sidebar]
+--
+For the most up-to-date API details, refer to {api-kibana}/group/endpoint-security-ai-assistant-api[AI Assistant APIs].
+--
+
 Apply a bulk action (create, update, or delete) to multiple anonymization fields. The bulk action is applied to all anonymization fields that match the filter or to the list of anonymization fields by their IDs.
 
 [discrete]

docs/AI-for-security/api/bulk-actions-anonymization-fields-api.asciidoc

@@ -1,6 +1,12 @@
 [[bulk-actions-prompts-api]]
 === Bulk prompt actions
 
+.New API Reference
+[sidebar]
+--
+For the most up-to-date API details, refer to {api-kibana}/group/endpoint-security-ai-assistant-api[AI Assistant APIs].
+--
+
 Apply a bulk action (create, update, or delete) to multiple prompts. The bulk action is applied to all prompts that match the filter or to the list of prompts by their IDs.
 
 [discrete]

docs/AI-for-security/api/bulk-actions-prompts-api.asciidoc

@@ -1,6 +1,12 @@
 [[chat-complete-api]]
 === Complete chat
 
+.New API Reference
+[sidebar]
+--
+For the most up-to-date API details, refer to {api-kibana}/group/endpoint-security-ai-assistant-api[AI Assistant APIs].
+--
+
 The complete chat API allows you to communicate with the configured large language model (LLM) and, if needed, persist the result as a conversation (create new or extend existing).
 
 [discrete]