Feature/faq prompt handling

[sandipan-fs]

Summary by CodeRabbit

• New Features

  • Added a full local development environment with Docker (backend, frontend, database, cache) and hot-reload.
  • Included developer tooling containers (pgAdmin, Redis Commander) and health checks for services.
  • Provided production-ready Docker images for backend and frontend.

• Documentation

  • Introduced comprehensive Development, Docker, and Azure DevOps guides.
  • Added Agent Builder integration and installation guides.
  • Updated README with Autonomize AI Studio branding and onboarding.

• Chores

  • Updated environment variables (added API URL; MCP composer flag renamed/disabled by default).
  • Revised license with proprietary and attribution sections.
  • Expanded ignore rules for auxiliary files.

[coderabbitai]

Walkthrough

Adds Azure DevOps CI/CD pipelines and reusable templates for backend and frontend, including a release step that updates a separate platform-charts repo. Introduces Dockerfiles and compose setups for backend/frontend. Adds multiple docs. Replaces numerous GitHub Actions workflows and issue templates by deleting them. Updates env, license, Makefile, and ignores.

Changes

Cohort / File(s)	Summary
Azure DevOps pipelines and templates .azure-pipelines/backend-cicd.yaml, .azure-pipelines/frontend-cicd.yaml, .azure-pipelines/templates/*, .azure-pipelines/variables/common.yml	New pipelines for backend/frontend with triggers; reusable build templates (Docker build/push); release template to update platform-charts service image tag; shared variables for ACR, runtimes, namespaces.
Docker configuration and images docker-compose.yml, docker-compose.dev.yml, docker/backend/Dockerfile, docker/frontend/Dockerfile, docker/build_and_push*.Dockerfile	Adds prod-like and dev compose stacks (backend, frontend, DB, cache, tooling); backend/frontend multi-stage Dockerfiles; sets RUSTFLAGS for reqwest in build Dockerfiles.
Documentation (added/updated) docs/AZURE_DEVOPS.md, docs/DEVELOPMENT.md, docs/DOCKER.md, README.md, AGENT_BUILDER_INTEGRATION_OVERVIEW.md, BUILDER_AGENT_INSTALL.md, CLAUDE.md	New/updated docs covering Azure DevOps, development, Docker, README rebrand, Agent Builder overview and install, and workflow guidelines.
GitHub Actions workflows and templates (removed) .github/workflows/*, .github/actions/install-playwright/action.yml, .github/ISSUE_TEMPLATE/*, .github/changes-filter.yaml, .github/dependabot.yml, .github/release.yml, .github/semantic.yml, .github/workflows/matchers/ruff.json	Deletes CI/test/release/security/docs workflows, composite action, issue templates, path filters, Dependabot, release and semantic configs, and Ruff matcher.
Cursor rules/docs (removed/edited) .cursor/rules/*.mdc, .cursor/settings.json	Removes multiple dev guideline rule files; updates Cursor settings by removing biome configuration path.
Config, env, and repo settings .env.example, .gitignore, config/.../_mcp_servers_*.json, config/secret_key, LICENSE, Makefile	Renames MCP composer flag; adds API URL var; extends .gitignore; adds empty MCP servers JSON and a secret key file; updates license text; Makefile adds DB setup and adjusts backend run command.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev
  participant AzurePipelines as Azure Pipelines
  participant TemplateBackend as backend-build-template.yml
  participant ACR as Azure Container Registry
  participant ChartsRepo as platform-charts (GitHub)

  Dev->>AzurePipelines: Push/PR to backend paths
  AzurePipelines->>TemplateBackend: Stage Build (params: repo, Dockerfile, BUILD_VERSION)
  TemplateBackend->>ACR: docker build & push (tags: BuildNumber, latest)
  AzurePipelines-->>AzurePipelines: Build Succeeded
  AzurePipelines->>ChartsRepo: Stage UpdatePlatformCharts (release-template.yml)
  ChartsRepo-->>ChartsRepo: Select values file by branch
  ChartsRepo-->>ChartsRepo: Update image tag via yq
  ChartsRepo->>ChartsRepo: Commit & push changes

Loading

sequenceDiagram
  autonumber
  actor Dev
  participant AzurePipelines as Azure Pipelines
  participant TemplateFrontend as frontend-build-template.yml
  participant ACR as Azure Container Registry
  participant ChartsRepo as platform-charts (GitHub)

  Dev->>AzurePipelines: Push/PR to frontend paths
  AzurePipelines->>TemplateFrontend: Stage Build (args: BUILD_VERSION, NODE_ENV)
  TemplateFrontend->>ACR: docker build & push (tags: BuildNumber, latest)
  AzurePipelines-->>AzurePipelines: Build Succeeded
  AzurePipelines->>ChartsRepo: Stage UpdatePlatformCharts (SERVICE_NAME, IMAGE_NAME)
  ChartsRepo-->>ChartsRepo: Update values file image tag
  ChartsRepo->>ChartsRepo: Commit & push

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

• chore: simplfied cross-platform test logic #9256 — Modifies cross-platform test workflow that this PR removes; overlaps on CI test orchestration.
• fix: Remove Docker duplicated build step from release workflow #8366 — Edits release workflow that this PR deletes; direct conflict on release automation.
• fix(langwatch): prevent trace errors with proper API key validation #9720 — Changes MCP composer flag similar to this PR’s .env.example update.

Suggested labels

enhancement, lgtm

Suggested reviewers

• lucaseduoli
• ogabrielluiz

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title “Feature/faq prompt handling” does not reflect the extensive changes in this pull request, which primarily add and remove CI/CD pipelines, documentation guidelines, Docker configurations, and project structure updates rather than introducing FAQ prompt handling. As a result, the title is misleading and unrelated to the actual scope of the changes.	Please update the pull request title to concisely describe the main changes, for example “Add Azure DevOps CI/CD pipelines and update project documentation” or split this large scope into more focused pull requests with matching titles.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate failed

Failed conditions
23 Security Hotspots
D Security Rating on New Code (required ≥ A)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[coderabbitai]

Actionable comments posted: 14

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

Makefile (1)

246-264: Do not combine uvicorn --reload with --workers.

Uvicorn forbids using reload with workers. Only set --workers when >1 and omit --reload then.

-        $(if $(filter-out 1,$(workers)),, --reload) \
+        $(if $(filter-out 1,$(workers)),, --reload) \
         --env-file $(env) \
         --loop asyncio \
-        $(if $(workers),--workers $(workers),)
+        $(if $(filter-out 1,$(workers)),--workers $(workers),)

Apply same change in both branches (autologin and else).

LICENSE (1)

1-52: Restore Langflow’s MIT license in LICENSE

• The LICENSE file currently replaces the MIT license with proprietary terms; revert to the original MIT license header. Proprietary notices must not override the OSS license in this repository.

🧹 Nitpick comments (9)

.gitignore (1)

278-287: Ignore local secret key file.

Add the committed secret path to .gitignore to prevent future leaks.

 *.mcp.json

 member_servers.json

 # AI Assistant working files
 CLAUDE.md
 SPEC_CREATION_PROMPT.md
 test_spec_conversion.py
+config/secret_key

README.md (1)

51-68: Add fenced code languages to satisfy markdownlint (MD040).

Specify a language for the ASCII diagram and project structure blocks, e.g., text.

-```
+```text
 # diagram...

-```
+```text
 ai-studio-service/
 ...

Also applies to: 175-185

docker-compose.yml (1)

19-25: Align services: use Postgres in backend and correct frontend BACKEND_URL.

• Backend currently uses SQLite while a Postgres service is defined. Point to database service for parity.
• Frontend build arg uses localhost; inside Compose, use the backend service name.

   environment:
-    - PYTHONPATH=/app
-    - LANGFLOW_DATABASE_URL=sqlite:///app/data/langflow.db
+    - PYTHONPATH=/app
+    - LANGFLOW_DATABASE_URL=postgresql+psycopg://aistudio:dev_password_change_in_production@database:5432/ai_studio
     - LANGFLOW_CACHE_TYPE=memory
     - LANGFLOW_LOG_LEVEL=DEBUG
     - HOST=0.0.0.0
     - PORT=7860

   args:
     BUILD_VERSION: local-dev
-    BACKEND_URL: http://localhost:7860
+    BACKEND_URL: http://backend:7860
     NODE_ENV: development

If SQLite is intentional, consider removing the Postgres service here or guard DB URL via an .env file.

Also applies to: 44-46

docker/backend/Dockerfile (1)

60-72: Consider a smaller base image for production.

Switching to python:3.12-slim (or distroless) can reduce image size and CVE surface.

.azure-pipelines/templates/backend-build-template.yml (1)

22-35: ACR parameter semantics and build gating.

• Docker@2 containerRegistry expects a service connection; the summary uses it as an ACR name. Consider separate params (service connection vs ACR login server) to avoid confusion.
• Build/push are gated to Manual/IndividualCI/BatchedCI; PullRequest builds won’t build images. Confirm this is intended.

Example:

parameters:
  - name: ACR_SERVICE_CONNECTION
    type: string
  - name: ACR_LOGIN_SERVER
    type: string  # e.g., myregistry.azurecr.io

# Use:
containerRegistry: '${{ parameters.ACR_SERVICE_CONNECTION }}'

# Summary:
echo "🐳 Image: ${{ parameters.ACR_LOGIN_SERVER }}/${{ parameters.CONTAINER_NAME }}:$(Build.BuildNumber)"

Also applies to: 40-49, 51-59

AGENT_BUILDER_INTEGRATION_OVERVIEW.md (1)

343-347: Add language to fenced block for consistency

Specify a language (e.g., text) for this diagram block to satisfy linters and improve rendering.

-```
+```text
 User Request → Langflow API → AgentBuilderService → 5 Genesis Engines → YAML Response
                     ↓
             Streaming Events (SSE) → Frontend Updates

</blockquote></details>
<details>
<summary>BUILDER_AGENT_INSTALL.md (1)</summary><blockquote>

`11-27`: **Specify languages on fenced code blocks**

Add appropriate languages to improve readability and pass linters.


Suggested updates:
- File tree: use text
```diff
-```
+```text
 src/backend/base/langflow/
 ...

• Single path block: use text

-```
+```text
 src/backend/base/langflow/initial_setup/builder_agent/BuilderAgent.json

• Log samples: use text

-```
+```text
 Creating/updating builder agent flow
 Builder agent flow created/updated successfully

• Endpoint block: use http or text

-```
+```http
 POST /api/v1/run/{flow_id}?stream=true

Also applies to: 45-47, 152-156, 246-250, 263-266

docs/AZURE_DEVOPS.md (1)

7-21: Annotate neutral code fences with an explicit language.

Plain triple backticks violate our docs rule that every code block must declare a language. Please tag this directory listing with something like text so the renderer and linters stay happy.

As per coding guidelines

-```
+```text
 ai-studio/
 ├── .azure-pipelines/
 │   ├── backend-cicd.yaml                   # Backend CI/CD pipeline
@@
     └── HELM.md                             # Helm chart documentation
 └── docs/
     ├── AZURE_DEVOPS.md                     # This document
     └── HELM.md                             # Helm chart documentation
-```
+```

docs/DOCKER.md (1)

7-18: Give this code fence a language label.

Every fenced block must declare a language. Mark this directory tree as text (or similar) to satisfy the docs style and linter.

As per coding guidelines

-```
+```text
 ai-studio/
 ├── docker/
 │   ├── backend/
@@
 └── docs/
     └── DOCKER.md                   # This documentation
-```
+```

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Prevent release stage from running on PRs

If Build is skipped on PRs, UpdatePlatformCharts can still meet succeeded() and run. Add the same PR guard.

 - stage: UpdatePlatformCharts
   displayName: 'Update Platform Charts'
   dependsOn: Build
-  condition: succeeded()
+  condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
   jobs:

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- stage: UpdatePlatformCharts
	displayName: 'Update Platform Charts'
	dependsOn: Build
	condition: succeeded()
	jobs:
	- template: templates/release-template.yml
	parameters:
	SERVICE_NAME: 'backend'
	IMAGE_NAME: $(IMAGE_NAME)
	- stage: UpdatePlatformCharts
	displayName: 'Update Platform Charts'
	dependsOn: Build
	condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
	jobs:
	- template: templates/release-template.yml
	parameters:
	SERVICE_NAME: 'backend'
	IMAGE_NAME: $(IMAGE_NAME)

🤖 Prompt for AI Agents

.azure-pipelines/backend-cicd.yaml around lines 76 to 85: the
UpdatePlatformCharts stage only uses condition: succeeded(), so it can still run
on PRs when Build is skipped; change the condition to include the same PR guard
used for Build, e.g. replace condition: succeeded() with condition:
and(succeeded(), ne(variables['Build.Reason'], 'PullRequest')) so the stage is
skipped for pull requests.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Prevent release stage from running on PRs

Mirror the Build stage PR guard on UpdatePlatformCharts to avoid pushing chart updates from PRs.

 - stage: UpdatePlatformCharts
   displayName: 'Update Platform Charts'
   dependsOn: Build
-  condition: succeeded()
+  condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
   jobs:

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- stage: UpdatePlatformCharts
	displayName: 'Update Platform Charts'
	dependsOn: Build
	condition: succeeded()
	jobs:
	- template: templates/release-template.yml
	parameters:
	SERVICE_NAME: 'frontend'
	IMAGE_NAME: $(IMAGE_NAME)
	- stage: UpdatePlatformCharts
	displayName: 'Update Platform Charts'
	dependsOn: Build
	condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
	jobs:
	- template: templates/release-template.yml
	parameters:
	SERVICE_NAME: 'frontend'
	IMAGE_NAME: $(IMAGE_NAME)

🤖 Prompt for AI Agents

In .azure-pipelines/frontend-cicd.yaml around lines 71 to 80, the
UpdatePlatformCharts stage lacks the PR guard used by the Build stage and can
run for PRs; add the same condition to prevent PR-triggered runs by setting the
stage condition to mirror Build, e.g. use condition: and(succeeded(),
ne(variables['Build.Reason'], 'PullRequest')) so the stage only runs on
successful non-PR builds.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix working directory and yq usage; export env for yq

Scripts run in the main repo by default, so git/yq act on the wrong repo. Also yq env() needs exported env var. Installing to /usr/local/bin may require sudo.

Apply:

   steps:
   - checkout: platform-charts
     fetchDepth: 0
     persistCredentials: true

-  - script: |
+  - script: |
       git config --global user.email "release@autonomize.ai"
       git config --global user.name "release"
       git checkout main
     displayName: 'Setup GIT'
+    workingDirectory: '$(Build.SourcesDirectory)/platform-charts'

-  - script: |
+  - script: |
       echo "Build Number: $(Build.BuildNumber)"
       echo "Source Branch: $(Build.SourceBranchName)"
-      wget -q https://github.com/mikefarah/yq/releases/download/v4.42.1/yq_linux_amd64
-      mv yq_linux_amd64 /usr/local/bin/yq
-      chmod +x /usr/local/bin/yq
+      wget -q -O yq https://github.com/mikefarah/yq/releases/download/v4.42.1/yq_linux_amd64
+      chmod +x ./yq
@@
-      buildnumber="$(Build.BuildNumber)" yq -i e '.genesis-studio.${{ parameters.SERVICE_NAME }}.image.tag = env(buildnumber)' $valuesFile
+      export buildnumber="$(Build.BuildNumber)"
+      ./yq -i e '.genesis-studio.${{ parameters.SERVICE_NAME }}.image.tag = env(buildnumber)' "$valuesFile"
@@
     displayName: 'Update Image Tags'
+    workingDirectory: '$(Build.SourcesDirectory)/platform-charts'

-  - script: |
+  - script: |
@@
       git add $valuesFile
       git commit -m "[skip ci] AI Studio ${{ parameters.SERVICE_NAME }} image tag updated: $(Build.BuildNumber) for $environment" || echo "No changes to commit"
       git push --set-upstream origin main
@@
     displayName: 'Commit and Push Changes'
+    workingDirectory: '$(Build.SourcesDirectory)/platform-charts'

Optional: add set -euo pipefail to scripts for robustness.

Also applies to: 23-49, 50-71

🤖 Prompt for AI Agents

In .azure-pipelines/templates/release-template.yml around lines 13-21, the
script runs in the main repo instead of the platform-charts checkout and uses yq
env() without exporting the env var and installs binary to /usr/local/bin
without sudo; update the script to run in the platform-charts working directory
(or set the checkout path for platform-charts and add a workingDirectory to the
script), export any environment variable that yq.env() reads (export VAR=value)
before invoking yq, and when moving the binary to /usr/local/bin either use sudo
or install to a user-writable path; apply the same fixes to the other script
blocks at lines 23-49 and 50-71, and optionally add set -euo pipefail at the top
of each script for robustness.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Confirm default value documentation

Comment now claims the MCP composer flag defaults to false. Please verify the application code actually uses False as its fallback so the doc and behavior stay aligned.

---

🏁 Script executed:

#!/bin/bash
# Locate server/client defaults for LANGFLOW_MCP_COMPOSER_ENABLED
rg -n "LANGFLOW_MCP_COMPOSER_ENABLED"

Length of output: 298

---

Align default value for LANGFLOW_MCP_COMPOSER_ENABLED

.env.example (lines 106–107) documents false as the default, but vite.config.mts falls back to "true", enabling the feature by default. Update the default in .env.example to true (or adjust the code fallback to false) so documentation and behavior match.

🤖 Prompt for AI Agents

In .env.example around lines 106–107, the documented default for
LANGFLOW_MCP_COMPOSER_ENABLED is "false" but the application (vite.config.mts)
falls back to "true", causing a mismatch; update .env.example to set
LANGFLOW_MCP_COMPOSER_ENABLED=true (or alternatively change the fallback in
vite.config.mts to "false") so the documented default and runtime behavior match
— pick one approach and apply it consistently across the env file and the code
fallback.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Replace absolute local paths with repo-relative paths

Hardcoded macOS user paths are not portable and break navigation. Point to repo-relative locations instead.

Example adjustments:

- - Schema: /Users/jagveersingh/Developer/studio/ai-studio/src/backend/base/langflow/specifications_library/documentation/schema/specification-schema.md
+ - Schema: src/backend/base/langflow/specifications_library/documentation/schema/specification-schema.md
- - Patterns: /Users/jagveersingh/Developer/studio/ai-studio/src/backend/base/langflow/specifications_library/documentation/patterns/pattern-catalog.md
+ - Patterns: src/backend/base/langflow/specifications_library/documentation/patterns/pattern-catalog.md
- - Components: /Users/jagveersingh/Developer/studio/ai-studio/src/backend/base/langflow/specifications_library/documentation/components/component-catalog.md
+ - Components: src/backend/base/langflow/specifications_library/documentation/components/component-catalog.md
- - Guide: /Users/jagveersingh/Developer/studio/ai-studio/src/backend/base/langflow/specifications_library/documentation/guides/creating-specifications.md
+ - Guide: src/backend/base/langflow/specifications_library/documentation/guides/creating-specifications.md

Also update later references to the same absolute prefix (validation service, components path, etc.) similarly. If this doc is internal-only, consider moving it under docs/ with proper links.

Also applies to: 13-16, 24-25, 284-287, 501-505, 637-641

🧰 Tools

🪛 LanguageTool

[grammar] ~7-~7: There might be a mistake here.
Context: ...mentation/schema/specification-schema.md - Patterns: /Users/jagveersingh/Developer/...

(QB_NEW_EN)

---

[grammar] ~8-~8: There might be a mistake here.
Context: ...ocumentation/patterns/pattern-catalog.md - Components: /Users/jagveersingh/Develope...

(QB_NEW_EN)

---

[grammar] ~9-~9: There might be a mistake here.
Context: ...entation/components/component-catalog.md - Guide: /Users/jagveersingh/Developer/stu...

(QB_NEW_EN)

🤖 Prompt for AI Agents

In CLAUDE.md around lines 7 to 11 (and also apply the same fix to ranges 13-16,
24-25, 284-287, 501-505, 637-641), replace the hardcoded absolute macOS user
paths with repo-relative paths (e.g., start with ./ or docs/ or the repository
root path) so links are portable; update all subsequent references that share
the same absolute prefix, ensure paths point to the correct files within the
repo (move the doc under docs/ if internal), and verify each updated link
resolves correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Correct the RUSTFLAGS value

The single quotes survive Docker parsing, so RUSTFLAGS becomes '--cfg reqwest_unstable', which Cargo hands to rustc as invalid flags. Switch to an unquoted or double-quoted value so the build actually enables the reqwest cfg.

-ENV RUSTFLAGS='--cfg reqwest_unstable'
+ENV RUSTFLAGS="--cfg reqwest_unstable"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	# Set RUSTFLAGS for reqwest unstable features needed by apify-client v2.0.0
	ENV RUSTFLAGS='--cfg reqwest_unstable'
	# Set RUSTFLAGS for reqwest unstable features needed by apify-client v2.0.0
	ENV RUSTFLAGS="--cfg reqwest_unstable"

🤖 Prompt for AI Agents

In docker/build_and_push_with_extras.Dockerfile around lines 23 to 25, the
RUSTFLAGS value is wrapped in single quotes which are preserved by Docker and
passed to rustc as invalid flags; change the ENV assignment to use an unquoted
or double-quoted value (for example: ENV RUSTFLAGS=--cfg reqwest_unstable or ENV
RUSTFLAGS="--cfg reqwest_unstable") so the cfg flag is passed correctly to
cargo/rustc.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Healthcheck needs curl installed.

The nginx Alpine image does not ship with curl, so the health check will fail immediately. Install curl (or use wget) in the runtime stage before you rely on it.

 FROM nginx:1.25-alpine
 
+# Install curl for health checks
+RUN apk add --no-cache curl
+
 # Copy custom nginx configuration
 COPY src/frontend/nginx.conf /etc/nginx/conf.d/default.conf

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	HEALTHCHECK --interval=30s --timeout=10s --start-period=5s --retries=3 \
	CMD curl -f http://localhost:3000 || exit 1
	FROM nginx:1.25-alpine
	# Install curl for health checks
	RUN apk add --no-cache curl
	# Copy custom nginx configuration
	COPY src/frontend/nginx.conf /etc/nginx/conf.d/default.conf
	HEALTHCHECK --interval=30s --timeout=10s --start-period=5s --retries=3 \
	CMD curl -f http://localhost:3000 || exit 1

🤖 Prompt for AI Agents

In docker/frontend/Dockerfile around lines 82 to 83, the HEALTHCHECK uses curl
but the nginx Alpine runtime stage doesn't include curl, causing immediate
failures; modify the runtime stage to install curl (or wget) before the
HEALTHCHECK is added—e.g., add a small apk add --no-cache curl (or wget) command
in the runtime stage so the binary is available at container runtime, then keep
the HEALTHCHECK as-is.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Add required front matter metadata.

Docs under docs/** must start with front matter that at least sets title, description, and (when applicable) sidebar_position. Please add it so this page renders correctly in the docs site navigation.

As per coding guidelines

+---
+title: "AI studio Azure DevOps organization guide"
+description: "Explain how you reorganize the Azure DevOps pipelines and templates for AI Studio."
+sidebar_position: 1
+---
 # AI Studio Azure DevOps Organization Guide

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	# AI Studio Azure DevOps Organization Guide
	This document provides detailed information about the reorganized Azure DevOps structure and pipeline integration with the unified Helm chart.
	---
	title: "AI studio Azure DevOps organization guide"
	description: "Explain how you reorganize the Azure DevOps pipelines and templates for AI Studio."
	sidebar_position: 1
	---
	# AI Studio Azure DevOps Organization Guide
	This document provides detailed information about the reorganized Azure DevOps structure and pipeline integration with the unified Helm chart.

🤖 Prompt for AI Agents

In docs/AZURE_DEVOPS.md around lines 1 to 4, the file is missing required front
matter for the docs site; add YAML front matter at the top including at minimum
title and description (and sidebar_position if this page should appear in the
sidebar). Populate title with a concise page title, description with a short
summary, and add sidebar_position when applicable, ensuring the front matter
block is wrapped between --- lines and placed before the existing content.

[coderabbitai]

🛠️ Refactor suggestion | 🟠 Major

Add required front matter and code fence language

Docs under docs/ must include front matter and specify languages for code blocks. Add title/description and set the first fence to text.

+---
+title: AI Studio development guide
+description: Set up, develop, test, and deploy AI Studio with Docker and Azure DevOps.
+sidebar_position: 1
+---
 # AI Studio Development Guide
@@
-```
+```text
 ai-studio/
 ├── src/
 ...

Also applies to: 7-23

<details>
<summary>🤖 Prompt for AI Agents</summary>

In docs/DEVELOPMENT.md around lines 1-3 (and also apply changes to lines 7-23),
the file is missing required front matter and the first code fence lacks a
language; add YAML front matter with title and description at the top (e.g.,
title and short description keys), and update the first fenced code block to use

appropriate language identifiers.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Insert the mandatory front matter block.

Docs need YAML front matter defining title, description, and a sidebar_position when published under docs/. Please add it so this guide integrates with the doc site correctly.

As per coding guidelines

+---
+title: "AI studio Docker setup guide"
+description: "Show how you build, run, and develop AI Studio with Docker and Compose."
+sidebar_position: 2
+---
 # AI Studio Docker Setup Guide

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	# AI Studio Docker Setup Guide
	This document provides comprehensive instructions for building, running, and developing AI Studio using Docker containers.
	---
	title: "AI studio Docker setup guide"
	description: "Show how you build, run, and develop AI Studio with Docker and Compose."
	sidebar_position: 2
	---
	# AI Studio Docker Setup Guide
	This document provides comprehensive instructions for building, running, and developing AI Studio using Docker containers.

🤖 Prompt for AI Agents

In docs/DOCKER.md around lines 1 to 4, the file is missing the required YAML
front matter (title, description, and sidebar_position) that docs/ requires for
proper site integration; add a top-of-file YAML block with keys title,
description, and sidebar_position (with appropriate values reflecting this
Docker guide) so the document publishes correctly in the docs site.