[RHDHBUGS-2953]: Resolve all existing CQA violations on main branch (#2052)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: themr0c

artifacts/attributes.adoc

@@ -202,5 +202,7 @@
 :upgrading-book-title: Upgrading {product}
 :using-dynamic-plugins-book-link: {product-docs-link}/html-single/using_dynamic_plugins_in_red_hat_developer_hub/index
 :using-dynamic-plugins-book-title: Using dynamic plugins in {product}
+:explore_preview_of_emerging_and_supplemental_capabilities-book-title: Explore preview of emerging and supplemental capabilities
+:explore_preview_of_emerging_and_supplemental_capabilities-book-link: {product-docs-link}/html-single/explore_preview_of_emerging_and_supplemental_capabilities/index
 
 

modules/configure_configuring-rhdh/proc-configure-an-rhdh-instance-with-a-tls-connection-in-kubernetes.adoc

@@ -6,6 +6,8 @@
 [role="_abstract"]
 Configure {product-very-short} with a TLS connection in Kubernetes to ensure secure connections with third-party applications and external databases.
 
+include::{docdir}/artifacts/snip-technology-preview.adoc[]
+
 .Prerequisites
 
 * You have set up an {azure-short} Red Hat OpenShift (ARO) cluster with a public CA-signed certificate. For more information about obtaining CA certificates, refer to your vendor documentation.

modules/observability_audit-logs-in-rhdh/ref-rbac-audit-log-events.adoc

@@ -32,15 +32,17 @@ RBAC audit logs contain a `meta` object with event-specific details:
 
 == Example audit log entries
 
-The following examples show how RBAC events appear in the {product-short} logs:
+The following examples show how RBAC events appear in the {product-short} logs.
+
+An RBAC role creation event with `status="initiated"`:
 
-.Example: RBAC role creation (initiated)
 [source,text]
 ----
 [backend]: 2025-03-25T17:24:17.438Z permission info permission.role-write isAuditEvent=true eventId="role-write" severityLevel="medium" actor={"actorId":"user:default/admin","ip":"::1"} request={"url":"/api/permission/roles","method":"POST"} meta={"actionType":"create", "source":"rest"} status="initiated"
 ----
 
-.Example: RBAC role creation (succeeded)
+An RBAC role creation event with `status="succeeded"`:
+
 [source,text]
 ----
 [backend]: 2025-03-25T17:24:17.458Z permission info permission.role-write isAuditEvent=true eventId="role-write" severityLevel="medium" actor={"actorId":"user:default/admin"} request={"url":"/api/permission/roles","method":"POST"} meta={"actionType":"create", "source":"rest","roleEntityRef":"role:default/test-role"} status="succeeded"

titles/additional-rhdh-capabilities/master.adoc

@@ -6,6 +6,10 @@ The content in this document describes preview or early-stage capabilities that
 
 Where applicable, individual features retain their respective support status (for example, Supported, Technology Preview, or Developer Preview). Refer to the feature-specific documentation for details about the link:https://access.redhat.com/support[support] scope.
 
+include::../artifacts/snip-technology-preview.adoc[]
+
+include::../artifacts/snip-developer-preview.adoc[]
+
 == Integrate Argo CD notifications with {product}
 
 This guide explains how to configure Argo CD to send notifications directly to the {product} ({product-very-short}) Notifications plugin when application sync events occur.
@@ -516,7 +520,7 @@ spec:
 
 === Troubleshooting
 
-==== Notifications not appearing in {product-very-short}
+=== Notifications not appearing in {product-very-short}
 
 1. **Check notifications controller is running:**
 +
@@ -553,7 +557,7 @@ kubectl get configmap argocd-notifications-cm -n openshift-gitops -o jsonpath='{
 kubectl get application my-app -n openshift-gitops -o jsonpath='{.metadata.annotations}' | jq .
 ----
 
-==== "notification service 'backstage' is not supported"
+=== "notification service 'backstage' is not supported"
 
 This error means the webhook service is not configured.
 
@@ -564,7 +568,7 @@ Common causes include the following:
 
 **Solution:** Use the `NotificationsConfiguration` CR for OpenShift GitOps (see Part 2).
 
-==== Webhook Returns 400 Bad Request / "not valid JSON"
+=== Webhook Returns 400 Bad Request / "not valid JSON"
 
 This means the trigger is using the wrong template format (text instead of JSON).
 
@@ -579,7 +583,7 @@ Common causes include the following:
 * Trigger: `trigger.on-sync-succeeded-backstage`
 * Subscription: `notifications.argoproj.io/subscribe.on-sync-succeeded-backstage.backstage`
 
-==== Link Shows *<no value>* or Broken URL
+=== Link Shows *<no value>* or Broken URL
 
 The `{{.context.argocdUrl}}` template variable is not configured.
 
@@ -606,7 +610,7 @@ data:
     argocdUrl: https://your-argocd-url.com
 ----
 
-==== Authentication Errors
+=== Authentication Errors
 
 If you see `401 Unauthorized` or token errors:
 

…lities/additional-rhdh-capabilities.adoc …lities/additional-rhdh-capabilities.adoctitles/additional-rhdh-capabilities/additional-capabilities/additional-rhdh-capabilities.adoc renamed to titles/additional_title-additional-rhdh-capabilities/additional-capabilities/additional-rhdh-capabilities.adoc titles/additional-rhdh-capabilities/additional-capabilities/additional-rhdh-capabilities.adoc renamed to titles/additional_title-additional-rhdh-capabilities/additional-capabilities/additional-rhdh-capabilities.adoc

@@ -0,0 +1,18 @@
+:_mod-docs-content-type: ASSEMBLY
+:_mod-docs-category: Additional
+
+include::artifacts/attributes.adoc[]
+:title: {explore_preview_of_emerging_and_supplemental_capabilities-book-title}
+:context: title-additional-rhdh-capabilities
+:subtitle: Explore features that are new, evolving, or not yet fully covered in the core product documentation
+:abstract: Explore emerging, evolving, and supplemental capabilities in {product}, including new features and supported functionality not yet fully covered in the core documentation.
+:imagesdir: images
+
+= {title}
+
+[role="_abstract"]
+{abstract}
+
+include::artifacts/snip-developer-preview.adoc[]
+
+include::additional-capabilities/additional-rhdh-capabilities.adoc[]