[auto] update translations

[github-actions]

Summary

Automated translation update triggered by changes to English documentation sources.

• Only changed pages were re-translated (content-hash cache)
• All 14 languages across 3 tiers (parallel matrix)

[hermes-exosphere]

Automated code review started - full review. Results will be posted here.

[hermes-exosphere]

⏳ Phase 0-2 complete — deep analysis done.

What this PR does: Adds 13 new language translations (ar, de, es, fr, he, hi, it, ja, ko, pt-br, ru, tr, vi) for the AgentEye documentation product, plus structural updates to (new AgentEye product tab, + pages added to all languages, case-renamed to , formatting normalization).

Scope: 281 files, 85K+ insertions, docs-only (no source code changes).

Findings so far:

• 21 translation files have a double frontmatter delimiter (3 '---' instead of 2) — linting concern
• All 300 referenced pages exist on disk, zero orphans
• All 14 translations match English page structure
• Group structure (Getting started / Deployment / Instrumentation and CLI / Quality / Operations) is consistent across all languages
• cli/auth and cli/audit correctly added to all 15 language entries
• pt-BR → pt-br rename is clean (no lingering references)

Now running Phase 3 — Build & Verify...

[hermes-exosphere]

⏳ Phase 0-2 complete — deep analysis done.

What this PR does: Adds 13 new language translations (ar, de, es, fr, he, hi, it, ja, ko, pt-br, ru, tr, vi) for the AgentEye documentation product, plus structural updates to docs.json (new AgentEye product tab, cli/auth + cli/audit pages added to all languages, pt-BR case-renamed to pt-br, formatting normalization).

Scope: 281 files, 85K+ insertions, docs-only (no source code changes).

Findings so far:

• 21 translation files have a double frontmatter delimiter (3 --- instead of 2) — linting concern
• All 300 referenced pages exist on disk, zero orphans
• All 14 translations match English page structure
• Group structure (Getting started / Deployment / Instrumentation and CLI / Quality / Operations) is consistent across all languages
• cli/auth and cli/audit correctly added to all 15 language entries
• pt-BR to pt-br rename is clean (no lingering references)

Now running Phase 3 — Build and Verify...

[hermes-exosphere]

Automated Code Review — PR #509

Executive Summary

This is an automated translation PR adding 13 new languages (ar, de, es, fr, he, hi, it, ja, ko, pt-br, ru, tr, vi) for the AgentEye documentation product. 281 files changed, 85K+ insertions, zero source code changes. Overall quality is solid — translations appear complete and structurally correct. One systemic frontmatter formatting issue found across 21 files.

---

Change Architecture

graph TD
    A[English docs/agenteye/*.mdx] -->|"translation pipeline"| B[14x translated docs/LANG/agenteye/*.mdx]
    A --> C[Updated docs/docs.json]
    C --> D["New AgentEye product tab"]
    C --> E["Formatting normalization"]
    C --> F["pt-BR to pt-br rename"]
    C --> G["+cli/auth +cli/audit to all 15 languages"]
    style B fill:#90EE90
    style D fill:#90EE90
    style F fill:#FFD700
    style G fill:#87CEEB

Loading

Legend: Green = New | Yellow = Breaking change risk | Blue = Modified

---

Breaking Changes

• Yellow: pt-BR to pt-br rename in docs.json — this is a breaking change for any downstream tooling that references the old casing. However, the rename appears intentional and complete (no lingering pt-BR references found).

Issues Found

1. Yellow Warning — 21 files have double frontmatter delimiters (3 --- lines instead of 2). Affected: ar (8 files), he (4), hi (2), it (3), tr (2), vi (2). Full list:

   • docs/ar/agenteye/audits.mdx, cli.mdx, evaluation-suite.mdx, getting-started.mdx, health-monitoring.mdx, single-pod-deployment.mdx, tenant-management.mdx, troubleshooting.mdx
   • docs/he/agenteye/assistant.mdx, deployment.mdx, evaluation-suite.mdx, getting-started.mdx
   • docs/hi/agenteye/cli-skill.mdx, managed-deployment.mdx
   • docs/it/agenteye/api-keys.mdx, managed-deployment.mdx, python-sdk.mdx
   • docs/tr/agenteye/github-token.mdx, troubleshooting.mdx
   • docs/vi/agenteye/alerts.mdx, managed-deployment.mdx

   This appears to be a bug in the translation automation pipeline — the English sources are clean. Mintlify may or may not handle this gracefully, but it's worth fixing for correctness.

Logical / Bug Analysis

• Structural validation: All 14 translations match English's page structure exactly. Each language has 20 pages across 5 groups (Getting started: 2, Deployment: 6, Instrumentation and CLI: 4, Quality: 3, Operations: 5). Zero missing or extra pages.
• File existence: All 300 referenced pages in docs.json exist on disk. Zero orphaned files (files on disk but not in docs.json).
• Group naming consistency: Group names follow a consistent pattern — English group names (Getting started, Deployment, etc.) are used as keys, with localized tab labels. This is correct Mintlify convention.
• docs.json changes: The existing FailproofAI product section got formatting normalization (multi-line arrays) and cli/auth + cli/audit pages added to all 15 languages. These changes are clean and consistent.
• No source changes: Zero changes to src/, package.json, __tests__/, or any non-docs files. No breaking API changes.

Evidence — Build and Test Results

CI Status

• CI workflow: Completed (action_required — awaiting approval for bot-authored PR)
• Supply Chain: Completed (action_required — same reason)

Since this PR changes only documentation files (no source code, no dependencies), the existing test suite is unaffected. The action_required status is expected for automated PRs from github-actions bot.

Structural Validation

AgentEye languages (15): en, zh, ja, ko, es, pt-br, de, fr, ru, hi, tr, vi, it, ar, he
English pages: 20
All translations match English page structure!
Group structure consistent across languages.
All 300 referenced files exist on disk.
No orphaned files.
All 14 translations correctly prefixed with lang code.

Issue Linkage

No linked issues found. This PR is a standalone automated translation update triggered by changes to English documentation sources.

Human Review Feedback

No human review comments on this PR.

Suggestions

1. Fix the translation pipeline: The double frontmatter delimiter issue (21 files across 6 languages) suggests a bug in the translation automation. The script generating translated MDX files should strip the empty leading --- block.

2. Consider adding a docs validation step: A quick lint check in CI (e.g., checking for exactly 2 --- delimiters in frontmatter, validating YAML frontmatter parses correctly) would catch this class of issue before it reaches PR review.

3. Verify Mintlify rendering: If possible, deploy a preview of these docs to confirm the double frontmatter doesn't cause rendering issues. Some MDX parsers silently tolerate it; others may break.

Verdict

VERDICT: APPROVED_WITH_SUGGESTIONS

The core translation work is solid — all pages are present, structurally correct, and no files are orphaned. The double frontmatter issue is cosmetic but systemic (21 files). Recommend fixing the pipeline to prevent recurrence, but this shouldn't block merge.

---

Automated code review · 2026-07-14 16:23:00 UTC

[hermes-exosphere]

Automated review: Approved with suggestions. See summary comment and inline notes for details. VERDICT: APPROVED_WITH_SUGGESTIONS

[hermes-exosphere]

Review complete.

Results:

• Phase 0: No prior review threads to resolve
• Phase 1-2: Full structural validation — all 300 pages present, all 14 translations match English structure, zero orphans
• Phase 3: CI shows action_required (expected for bot-authored PRs); no source changes = existing tests unaffected
• Phase 4: 14 inline comments posted for double frontmatter issue, summary posted, formal review submitted

Verdict: APPROVED_WITH_SUGGESTIONS — 21 files have a cosmetic frontmatter formatting issue (double --- delimiter) that should be fixed in the translation pipeline.