Merge main and nest Claude Code docs under existing AI assistants section

Resolve nav.adoc conflict by nesting Claude Code configuration persistence
pages under the existing "Using AI assistants in workspaces" section from
main, instead of a separate "AI coding tools in workspaces" section.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Oleksii Kurinnyi <okurinny@redhat.com>

Author: akurinnoy

.github/workflows/preview-sticky-comment.yml

@@ -18,10 +18,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: create
-        uses: actions-cool/maintain-one-comment@v3
+        uses: marocchino/sticky-pull-request-comment@v2
         with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          body: |
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          message: |
             ⚡️ Deploying pull request preview...
-            <!-- Sticky Pull Request Comment -->
-          body-include: "<!-- Sticky Pull Request Comment -->"

.github/workflows/publish-netlify.yml

@@ -47,11 +47,9 @@ jobs:
           NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
 
       - name: Update status comment
-        uses: actions-cool/maintain-one-comment@v3
+        uses: marocchino/sticky-pull-request-comment@v2
         with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          body: |
-            🎊 Navigate the preview: ${{ steps.netlify-publish.outputs.NETLIFY_URL }} 🎊
-            <!-- Sticky Pull Request Comment -->
-          body-include: "<!-- Sticky Pull Request Comment -->"
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           number: ${{ steps.vars.outputs.pr_number }}
+          message: |
+            🎊 Navigate the preview: ${{ steps.netlify-publish.outputs.NETLIFY_URL }} 🎊

0001-fix-Make-Discover-the-first-top-level-section-per-SM.patch

@@ -0,0 +1,52 @@
+From 3a08d09838b9f195c37b1621f8e5ca99cda998ad Mon Sep 17 00:00:00 2001
+From: Gaurav Trivedi <gtrivedi@redhat.com>
+Date: Tue, 16 Jun 2026 19:59:42 +0530
+Subject: [PATCH] fix: Make Discover the first top-level section per SME
+ feedback
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Addresses SME feedback from ibuziuk on PR #3098:
+- Move Discover to first position in navigation
+- Include 'Introduction to Che' and 'Eclipse Che hosted by Red Hat' in Discover section
+- Remove redundant overview and hosted-che from main nav (content accessible via Discover)
+- Logical user flow: Discover → Use → Administer
+
+This creates a better user journey where users first discover what Eclipse Che
+is and explore hosted options before diving into detailed architecture.
+
+Co-Authored-By: Claude Sonnet 4 <noreply@anthropic.com>
+---
+ antora.yml                | 2 --
+ modules/discover/nav.adoc | 2 ++
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/antora.yml b/antora.yml
+index 805ff274..f40b9f10 100644
+--- a/antora.yml
++++ b/antora.yml
+@@ -5,8 +5,6 @@ version: next
+ prerelease: true
+ start_page: overview:introduction-to-eclipse-che.adoc
+ nav:
+-  - modules/overview/nav.adoc
+-  - modules/hosted-che/nav.adoc
+   - modules/discover/nav.adoc
+   - modules/end-user-guide/nav.adoc
+   - modules/administration-guide/nav.adoc
+diff --git a/modules/discover/nav.adoc b/modules/discover/nav.adoc
+index d21c3f64..f6f27c59 100644
+--- a/modules/discover/nav.adoc
++++ b/modules/discover/nav.adoc
+@@ -1,5 +1,7 @@
+ .Discover
+ 
++* xref:overview:introduction-to-eclipse-che.adoc[]
++* xref:hosted-che:hosted-che.adoc[]
+ * xref:architecture-overview.adoc[]
+ ** xref:server-components.adoc[]
+ *** xref:che-operator.adoc[]
+-- 
+2.54.0
+

antora.yml

@@ -5,8 +5,8 @@ version: next
 prerelease: true
 start_page: overview:introduction-to-eclipse-che.adoc
 nav:
-  - modules/overview/nav.adoc
-  - modules/hosted-che/nav.adoc
+  - modules/discover/nav.adoc
+  - modules/install/nav.adoc
   - modules/end-user-guide/nav.adoc
   - modules/administration-guide/nav.adoc
   - modules/extensions/nav.adoc
@@ -98,8 +98,8 @@ asciidoc:
     prod-upstream: Eclipse Che
     prod-url: "https://__<che_fqdn>__"
     prod-ver-major: "7"
-    prod-ver-patch: "7.118.0"
-    prod-ver: "7.118"
+    prod-ver-patch: "7.119.0"
+    prod-ver: "7.119"
     prod-workspace: che-ws
     prod: Eclipse Che
     prod2: Eclipse Che
@@ -133,6 +133,6 @@ ext:
   - run:
       command: ./tools/create_architecture_diagrams.py
     scan:
-      base: modules/administration-guide/images/architecture/
+      base: modules/discover/images/architecture/
       dir: build/collector/architecture-diagrams
       files: '*.png'

modules/administration-guide/examples/proc_che-configuring-ingresses.adoc

@@ -26,6 +26,6 @@ spec:
 
 .Additional resources
 
-* xref:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
+* xref:install:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
 
 * xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]

modules/administration-guide/examples/snip_che-concealing-editors-additional-resources.adoc

@@ -2,7 +2,7 @@
 
 .Additional resources
 
-* xref:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
+* xref:install:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
 
 * xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]
 

modules/administration-guide/examples/snip_che-upgrading-the-chectl-management-tool.adoc

@@ -4,7 +4,7 @@ This section describes how to upgrade the `{prod-cli}` management tool.
 
 .Prerequisites
 
-* `{prod-cli}`. See: xref:installing-the-chectl-management-tool.adoc[].
+* `{prod-cli}`. See: xref:install:installing-the-chectl-management-tool.adoc[].
 
 .Procedure
 

modules/administration-guide/nav.adoc

@@ -1,44 +1,9 @@
 .Administration Guide
 
 * xref:security-best-practices.adoc[]
-* xref:preparing-the-installation.adoc[]
-** xref:supported-platforms.adoc[]
-** xref:installing-the-chectl-management-tool.adoc[]
-** xref:architecture-overview.adoc[]
-*** xref:server-components.adoc[]
-**** xref:che-operator.adoc[]
-**** xref:devworkspace-operator.adoc[]
-**** xref:gateway.adoc[]
-**** xref:dashboard.adoc[]
-**** xref:che-server.adoc[]
-**** xref:che-devfile-registry.adoc[]
-**** xref:plugin-registry.adoc[]
-*** xref:user-workspaces.adoc[]
-** xref:calculating-che-resource-requirements.adoc[]
-* xref:running-at-scale.adoc[]
-// Install
-* xref:installing-che.adoc[]
-** Deploy on OpenShift
-*** xref:proc_installing-che-on-openshift-using-cli.adoc[]
-*** xref:proc_installing-che-on-openshift-using-the-web-console.adoc[]
-*** xref:proc_installing-che-on-openshift-with-keycloak-as-oidc.adoc[]
-** Deploy on {kubernetes}
-*** xref:installing-che-on-microsoft-azure.adoc[]
-*** xref:installing-che-on-amazon-elastic-kubernetes-service.adoc[]
-*** xref:proc_installing-che-on-the-virtual-kubernetes-cluster.adoc[]
-** Deploy locally
-*** xref:proc_installing-che-on-red-hat-openshift-local.adoc[]
-*** xref:proc_installing-che-on-minikube.adoc[]
-*** xref:proc_installing-che-on-minikube-keycloak-oidc.adoc[]
-** Deploy in a restricted environment
-*** xref:proc_installing-che-in-a-restricted-environment.adoc[]
-** xref:proc_finding-the-fully-qualified-domain-name-fqdn.adoc[]
-** xref:permissions-to-install-che.adoc[]
-*** xref:ref_permissions-to-install-che-on-openshift-using-cli.adoc[]
-*** xref:ref_permissions-to-install-che-on-openshift-using-the-web-console.adoc[]
 * xref:configuring-che.adoc[]
 ** xref:understanding-the-checluster-custom-resource.adoc[]
-*** xref:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
+*** xref:install:using-chectl-to-configure-the-checluster-custom-resource-during-installation.adoc[]
 *** xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]
 *** xref:checluster-custom-resource-fields-reference.adoc[]
 ** xref:configuring-namespace-provisioning.adoc[]
@@ -97,6 +62,8 @@
 *** xref:configuring-default-editor.adoc[]
 *** xref:concealing-editors.adoc[]
 *** xref:configuring-editors-download-urls.adoc[]
+*** xref:configuring-ai-providers.adoc[]
+**** xref:ai-provider-api-key-secret-reference.adoc[]
 *** xref:customizing-openshift-che-branding-images.adoc[]
 ** xref:managing-identities-and-authorizations.adoc[]
 *** xref:configuring-oauth-for-git-providers.adoc[]
@@ -137,4 +104,3 @@
 ** xref:upgrading-che-using-the-cli-management-tool.adoc[]
 ** xref:upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc[]
 ** xref:repairing-the-devworkspace-operator-on-openshift.adoc[]
-* xref:proc_uninstalling-che.adoc[]

modules/administration-guide/pages/ai-provider-api-key-secret-reference.adoc

@@ -0,0 +1,108 @@
+:_content-type: REFERENCE
+:description: Kubernetes Secret schema, labels, and naming convention for AI provider API keys that are automatically mounted into workspace containers.
+:keywords: administration, ai, api key, secret, kubernetes, devworkspace controller, environment variable, mount
+:navtitle: AI provider API key secret reference
+:page-aliases:
+
+[id="ai-provider-api-key-secret-reference"]
+= AI provider API key secret reference
+
+[role="_abstract"]
+Each user's AI provider API key is stored as a {kubernetes} `Opaque` Secret in the user's personal {orch-namespace}. The {devworkspace} Controller automatically mounts matching Secrets as environment variables into all workspace containers. Use this reference when manually creating or troubleshooting AI provider key Secrets.
+
+== Secret schema
+
+[source,yaml,subs="+quotes,+attributes"]
+----
+apiVersion: v1
+kind: Secret
+metadata:
+  name: ai-provider-openai-api-key   <1>
+  namespace: __<user-namespace>__
+  labels:
+    controller.devfile.io/mount-to-devworkspace: 'true'  <2>
+    controller.devfile.io/watch-secret: 'true'           <3>
+    che.eclipse.org/ai-provider-id: opencodeai-opencode  <4>
+  annotations:
+    controller.devfile.io/mount-as: env                  <5>
+type: Opaque
+data:
+  OPENAI_API_KEY: __<base64-encoded-api-key>__           <6>
+----
+<1> Secret name is derived as `ai-provider-` + `envVarName.toLowerCase().replace(/_/g, '-')`. For `OPENAI_API_KEY` the name is `ai-provider-openai-api-key`.
+<2> Instructs the DevWorkspace Controller to mount this Secret into all `DevWorkspace` containers in the namespace.
+<3> Instructs the DevWorkspace Controller to watch for Secret changes and re-mount without a workspace restart.
+<4> Sanitized provider ID (characters other than letters, digits, dots, underscores, and dashes are replaced with dashes). Identifies which AI provider this Secret belongs to. Used by the {prod-short} dashboard to detect existing keys.
+<5> Mounts the Secret data keys as environment variables (not as files).
+<6> The data key is the environment variable name. The value is base64-encoded. The variable is injected directly into all workspace containers.
+
+== Label and annotation reference
+
+[cols="1,1,2",options="header"]
+|===
+| Label / Annotation | Value | Purpose
+
+| `controller.devfile.io/mount-to-devworkspace`
+| `'true'`
+| Causes the DevWorkspace Controller to mount this Secret into every `DevWorkspace` in the namespace.
+
+| `controller.devfile.io/watch-secret`
+| `'true'`
+| The DevWorkspace Controller re-mounts the Secret when its data changes, without requiring a workspace restart.
+
+| `controller.devfile.io/mount-as`
+| `env`
+| Each data key in the Secret becomes an environment variable with the key as the variable name and the decoded value as the variable value.
+
+| `che.eclipse.org/ai-provider-id`
+| Sanitized provider ID (for example, `opencodeai-opencode`). Characters other than letters, digits, dots, underscores, and dashes are replaced with dashes.
+| Used by the {prod-short} dashboard to identify and list AI provider key Secrets when rendering the AI Selector widget.
+|===
+
+== Secret naming convention
+
+Secret names follow the pattern:
+
+----
+ai-provider-<envVarName-lowercased-underscores-as-dashes>
+----
+
+Example:
+
+[cols="1,1",options="header"]
+|===
+| `envVarName` | Secret name
+
+| `OPENAI_API_KEY`
+| `ai-provider-openai-api-key`
+|===
+
+== Manual Secret creation
+
+Advanced users can create AI provider key Secrets manually using `{orch-cli}` instead of the dashboard UI. Use the same labels and annotations as shown in the schema above:
+
+[subs="+quotes,+attributes"]
+----
+$ {orch-cli} apply -f - <<EOF
+apiVersion: v1
+kind: Secret
+metadata:
+  name: ai-provider-openai-api-key
+  namespace: __<user-namespace>__
+  labels:
+    controller.devfile.io/mount-to-devworkspace: 'true'
+    controller.devfile.io/watch-secret: 'true'
+    che.eclipse.org/ai-provider-id: opencodeai-opencode
+  annotations:
+    controller.devfile.io/mount-as: env
+type: Opaque
+data:
+  OPENAI_API_KEY: __<base64-encoded-api-key>__
+EOF
+----
+
+.Additional resources
+
+* xref:configuring-ai-providers.adoc[]
+* xref:end-user-guide:mounting-secrets.adoc[Mounting secrets (end-user guide)]
+* link:https://devfile.io/docs/2.2.0/what-is-a-devfile[Devfile documentation]