docs: add Highflame observability integration

[KunalJavelin]

Adds a Highflame page under Observability.

Highflame provides runtime AI security guardrails — prompt injection, sensitive-information / PII & DLP, content safety — for CrewAI via Highflame Shield, organized around the OWASP LLM Top 10. It integrates through the BaseEventListener-based HighflameCrewHooks (pip install 'highflame[crewai]'), guarding every LLM and tool call your crew makes.

• Adds docs/en/observability/highflame.mdx, modeled on the existing Portkey observability page.
• Adds ar/ko/pt-BR copies (English pending translation).
• Registers en/observability/highflame in the Observability navigation.

⚠️ This PR was AI-assisted. Per CONTRIBUTING it should carry the llm-generated label — I don't have permission to add labels on this repo, so could a maintainer please apply it? Thanks!

Summary by CodeRabbit

• Documentation
  • Added an additional observability documentation entry to the knowledge base.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20b9389c-c129-46ad-9700-017c4d2b1857

📥 Commits

Reviewing files that changed from the base of the PR and between 0a30265 and 5ed31f6.

📒 Files selected for processing (1)

• docs/docs.json

💤 Files with no reviewable changes (1)

• docs/docs.json

---

📝 Walkthrough

Walkthrough

A single entry, "edge/en/observability/highflame", is added to docs/docs.json immediately after "edge/en/observability/portkey".

Changes

Highflame Docs Manifest Entry

Layer / File(s)	Summary
Docs manifest registration docs/docs.json	Adds "edge/en/observability/highflame" to the navigation list directly after the "edge/en/observability/portkey" entry.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding a Highflame observability integration to the docs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[coderabbitai]

Caution

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

⚠️ Outside diff range comments (1)

docs/ar/observability/highflame.mdx (1)

1-76: ⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Translation files contain English content instead of translated text.

All three translation files (Arabic, Korean, Portuguese-Brazil) currently contain identical English content. According to the contributing guidelines, translations must maintain parity by translating natural language text while preserving code blocks, URLs, and MDX/JSX syntax unchanged. These files should not be merged until properly translated, as they will serve broken content to non-English speaking users.

Required changes for each file:

• Translate frontmatter fields (title, description)
• Translate all body text (headings, paragraphs, table content, note text)
• Keep code blocks, URLs, and MDX components (<Steps>, <Step>, <Note>) unchanged

As per coding guidelines: "Update translations in docs/{ar,ko,pt-BR}/ to maintain parity" and "Keep all MDX/JSX syntax, code blocks, and URLs unchanged in translations."

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/ar/observability/highflame.mdx` around lines 1 - 76, The Arabic
translation file docs/ar/observability/highflame.mdx currently contains the
original English content; update the file to provide a proper Arabic translation
while preserving all MDX/JSX, code blocks, URLs and component tags. Specifically
translate the frontmatter fields title and description, all headings and body
text (e.g., "# Highflame", "## Setup", "## Modes", the table content and list
items like "LLM01 Prompt Injection"), and the <Note> paragraph into Arabic, but
do not change any code blocks (the pip install and Python snippet), the
Highflame/HighflameCrewHooks names, URLs, or the <Steps>/<Step>/<Note>
components and their attributes. Repeat the same parity rules for the other
untranslated files mentioned (ko and pt-BR) so translations match the original
English structure.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@docs/ar/observability/highflame.mdx`:
- Around line 1-76: The Arabic translation file
docs/ar/observability/highflame.mdx currently contains the original English
content; update the file to provide a proper Arabic translation while preserving
all MDX/JSX, code blocks, URLs and component tags. Specifically translate the
frontmatter fields title and description, all headings and body text (e.g., "#
Highflame", "## Setup", "## Modes", the table content and list items like "LLM01
Prompt Injection"), and the <Note> paragraph into Arabic, but do not change any
code blocks (the pip install and Python snippet), the
Highflame/HighflameCrewHooks names, URLs, or the <Steps>/<Step>/<Note>
components and their attributes. Repeat the same parity rules for the other
untranslated files mentioned (ko and pt-BR) so translations match the original
English structure.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 29dc4d3b-cb68-4d05-93b5-857f54309050

📥 Commits

Reviewing files that changed from the base of the PR and between da8fe8c and 287ede2.

📒 Files selected for processing (5)

• docs/ar/observability/highflame.mdx
• docs/docs.json
• docs/en/observability/highflame.mdx
• docs/ko/observability/highflame.mdx
• docs/pt-BR/observability/highflame.mdx

[KunalJavelin]

@greysonlalonde would you be the right reviewer for this? It adds a Highflame observability page (runtime guardrails for CrewAI via the BaseEventListener-based HighflameCrewHooks), modeled on the existing Portkey page. I've trimmed it to an English-only page (dropped the untranslated locale copies CodeRabbit flagged). One ask: I don't have permission to add labels, so could a maintainer apply llm-generated per CONTRIBUTING? Thanks!

[KunalJavelin]

Follow-up @greysonlalonde — rebased on latest main (resolved the conflict from the recent docs restructure; the page now lives under edge/en/observability/). CodeRabbit approved, and I trimmed it to an English-only page. Could a maintainer also apply the llm-generated label per CONTRIBUTING? Thanks!