test: docs/serverless backport workflow research (authorized, will self-close)

.backportrc.json

@@ -1,5 +1,5 @@
 {
   "upstream": "elastic/security-docs",
-  "branches": [{ "name": "7.x", "checked": true }, "8.4", "8.3", "8.2", "8.1", "8.0", "7.17", "7.16", "7.15", "7.14", "7.13", "7.12", "7.11", "7.10", "7.9", "7.8"],
+  "branches": ["8.x", "8.18", "8.17", "8.16", "8.15", "8.14", "8.13", "8.12", "8.11", "8.10", "8.9", "8.8", "8.7", "8.6", "8.5", "8.4", "8.3", "8.2", "8.1", "8.0", "7.17", "7.16", "7.15", "7.14", "7.13", "7.12", "7.11", "7.10", "7.9", "7.8"],
   "labels": ["backport"]
 }

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+* @elastic/security-docs
+/.github/workflows/co-docs-builder.yml @elastic/docs-engineering

.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/bug-report.yaml

@@ -0,0 +1,58 @@
+name: "Bug report"
+description: "Report a bug in the Elastic Security documentation"
+title: "[BUG] "
+labels: "bug"
+body: 
+  - type: markdown
+    attributes:
+      value: |
+        Hello! Use this form to report an Elastic Security documentation bug to the [@elastic/security-docs](https://github.com/orgs/elastic/teams/security-docs) team.
+  - type: textarea
+    id: doc-links
+    attributes:
+      label: Documentation links
+      description: Which doc(s) is affected?
+      placeholder: |
+        Elastic Security overview: https://www.elastic.co/guide/en/security/current/es-overview.html
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the bug. What needs to be removed, edited, added, or replaced? Please also include instructions on how to reproduce the bug, if necessary. 
+    validations:
+      required: true
+  - type: dropdown
+    id: doc-set
+    attributes:
+      label: Which documentation set(s) does this bug apply to?
+      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 bug applies to. 
+      placeholder: |
+        For example:
+        "This bug applies to Stack versions 8.10 and newer." 
+         "N/A"
+    validations:
+      required: false
+  - type: textarea
+    id: testing-env
+    attributes:
+      label: Testing environment
+      description: Please include the URL to the server or test environment, or include instructions on how to generate test data. 
+      placeholder: |
+        You can find this in the Kibana dev server: https://kibana.siem.estc.dev/
+    validations:
+      required: true

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

@@ -0,0 +1,100 @@
+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
+    attributes:
+      value: |
+        Hello! This form will create an issue that the Security docs team will triage and prioritize. Please do not add any labels to your issue — we'll take care of that.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe what needs to be documented. What details do users need to know about? What are typical workflows for the feature?
+      placeholder: |
+        What: We're introducing new feature A.
+        Why: This feature will make X, Y, and Z easier for the user.
+        How: The user navigates to *Foo* → *Bar*, then clicks the *Wow* button.
+    validations:
+      required: true
+  - type: textarea
+    id: related
+    attributes:
+      label: Background & resources
+      description: |
+        Please include relevant pull requests or issues, and at least one point of contact. 
+        Also include any test environments where we can access the feature, and list steps to generate data we can test. 
+      value: |
+        * PRs: 
+        * Issues/metas: 
+        * Point of contact: 
+        * Test environments: 
+    validations:
+      required: true
+  - type: dropdown
+    id: doc-set
+    attributes:
+      label: Which documentation set does this change impact?
+      description: ESS (classic), serverless, or both?
+      options:
+        - ESS and serverless
+        - ESS only
+        - Serverless only
+        - Unknown
+      default: 0
+    validations:
+      required: true
+  - type: textarea
+    id: version-ess
+    attributes:
+      label: ESS release
+      description: Please provide a release version if your request is tied to the Elastic Stack release schedule.
+      placeholder: |
+        For example:
+        "The functionality is being introduced in ESS version 8.18.0"
+    validations:
+      required: true
+  - type: input
+    id: release-serverless
+    attributes:
+      label: Serverless release
+      description: When do you expect the feature to be promoted and available in the _**serverless production environment**_?
+      placeholder: The week of April 1, 2024
+    validations:
+      required: true
+  - type: textarea
+    id: doc-set-differences
+    attributes:
+      label: Feature differences
+      description: If you selected both ESS and serverless above, please describe how, if at all, the feature differs in each platform.
+      placeholder: The feature is identical in ESS and serverless.
+    validations:
+      required: true
+  - type: textarea
+    id: api-docs
+    attributes:
+      label: API docs impact
+      description: Please provide endpoint and parameter descriptions, and request and response examples.
+      placeholder: |
+        What: We're introducing new endpoint A.
+        Why: Users can send a request to endpoint A to use feature A.
+        How: The user provides the specific information in the request.   
+    validations:
+      required: true      
+  - type: textarea
+    id: prereqs
+    attributes:
+      label: Prerequisites, privileges, feature flags
+      description: |
+        What are the feature's requirements _**in both ESS and serverless**_? What subscription tiers or user role privileges are required?
+        Is the feature behind a feature flag, and if so, what is it?
+      placeholder: |
+        * ESS: Requires Enterprise subscription; `write` privilege for `yada-yada-*` index
+        * Serverless: Requires Security Analytics Complete tier and Endpoint Protection Complete add-on; X, Y, or Z user roles
+        * Feature flag: None
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for completing this form to help us understand and plan accordingly. We'll be in touch soon!

.github/ISSUE_TEMPLATE/enhancement-request.yaml

@@ -0,0 +1,58 @@
+name: "Request a documentation improvement"
+description: Request a change to improve Elastic Security docs.
+title: "[Suggestion] "
+labels: "suggestion"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        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: 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. 
+    validations:
+      required: true
+  - type: textarea
+    id: related
+    attributes:
+      label: Doc URL
+      description: How can we learn more about the problem?
+      value: |
+        Please include the doc URL and any other related information where applicable:
+        Doc URL: 
+        Github issue link(s)/Other resources:
+    validations:
+      required: false
+  - type: dropdown
+    id: doc-set
+    attributes:
+      label: Which documentation set needs improvement?
+      description: ESS, serverless, or both?
+      options:
+        - ESS and serverless
+        - ESS only
+        - Serverless only
+        - Unknown / Not applicable
+      default: 0
+    validations:
+      required: true
+  - type: textarea
+    id: software-version
+    attributes:
+      label: Software version
+      description: Is the problem applicable to a particular release version? If so, which one(s)?
+      placeholder: |
+        For example:
+        "The functionality was introduced in 8.11.0, so docs need updating for 8.11+"; 
+        "The docs are good after version 8.10, but need updating in 8.7, 8.8, and 8.9"
+    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.