guardrail docs fixes

[Madhuvod]

Summary

Briefly explain the purpose of this PR and the problem it solves.

Changes

• What was changed and why
• Any notable design decisions or trade-offs

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Describe the steps to validate this change. Include commands and expected outcomes.

# Core/Transports
go version
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

If adding new configs or environment variables, document them here.

Screenshots/Recordings

If UI changes, add before/after screenshots or short clips.

Breaking changes

• Yes
• No

If yes, describe impact and migration instructions.

Related issues

Link related issues and discussions. Example: Closes #123

Security considerations

Note any security implications (auth, secrets, PII, sandboxing, etc.).

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Clarified that linked guardrail profiles are evaluated in order and processing stops when a profile intervenes or fails.
  • Expanded AWS Bedrock authentication options, credential configuration, supported regions, and setup examples.
  • Documented API key and Entra ID authentication options for Azure Content Safety.
  • Added configurable base URL guidance for the Gray Swan Cygnal integration.

Walkthrough

Changes

Guardrails documentation

Layer / File(s)	Summary
Profile execution behavior docs/enterprise/guardrails.mdx	Clarifies that linked profiles run in configured order and stop when a profile intervenes or fails.
Provider authentication configuration docs/integrations/guardrails/aws-bedrock.mdx, docs/integrations/guardrails/azure-content-safety.mdx	Documents AWS Bedrock API key, IAM role, default credential chain, and Azure Entra ID authentication options.
Provider endpoints and regions docs/integrations/guardrails/aws-bedrock.mdx, docs/integrations/guardrails/grayswan.mdx	Expands supported AWS regions and documents the Gray Swan base_url option and accepted URL formats.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: akshaydeo, pratham-mishra04

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is just the unchanged template and lacks a real summary, changes, testing, related issues, and security details.	Replace the template with a filled-out PR description covering summary, changes, affected areas, testing steps, related issues, and security considerations.
Linked Issues check	⚠️ Warning	The changes update guardrail documentation only and do not address Files API support or a /v1/files endpoint for issue #123.	Implement the Files API support described in #123, including file upload handling and provider integration for workflows like RAG and fine-tuning.
Out of Scope Changes check	⚠️ Warning	All modified files are guardrail docs updates and are unrelated to the linked Files API support objective.	Either retarget the PR to the Files API work in #123 or remove the guardrail documentation changes as out-of-scope.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the documentation-focused guardrail changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-24-guardrail_docs_fixes

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/integrations/guardrails/aws-bedrock.mdx (1)

29-29: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Make auth_type: inferred deterministic in the docs.

The table introduces three conditional credential modes, but inferred does not explain precedence when multiple credential sources are present. Either document the inference rules or add "auth_type": "keys" to the static-credentials example.

As per path instructions, conditional authentication settings should document the selector, mode-specific fields, and defaults.

🤖 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/integrations/guardrails/aws-bedrock.mdx` at line 29, Update the AWS
Bedrock integration documentation around the auth_type table and
static-credentials example to make conditional authentication deterministic:
either document the precedence rules for inferred credential-source selection,
or explicitly set auth_type to keys in the static-credentials example. Ensure
the documentation covers the selector, mode-specific fields, and defaults.

Source: Path instructions

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

Inline comments:
In `@docs/integrations/guardrails/azure-content-safety.mdx`:
- Line 34: Update the scopes row in the Azure Content Safety integration options
table to replace “Azure default” with the explicit default array
["https://cognitiveservices.azure.com/.default"], and state that this default
applies to Entra ID token authentication.

---

Nitpick comments:
In `@docs/integrations/guardrails/aws-bedrock.mdx`:
- Line 29: Update the AWS Bedrock integration documentation around the auth_type
table and static-credentials example to make conditional authentication
deterministic: either document the precedence rules for inferred
credential-source selection, or explicitly set auth_type to keys in the
static-credentials example. Ensure the documentation covers the selector,
mode-specific fields, and defaults.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: dddd2a0c-8648-4662-a7e7-9f1c93158de0

📥 Commits

Reviewing files that changed from the base of the PR and between 28d828a and bdafbe7.

📒 Files selected for processing (4)

• docs/enterprise/guardrails.mdx
• docs/integrations/guardrails/aws-bedrock.mdx
• docs/integrations/guardrails/azure-content-safety.mdx
• docs/integrations/guardrails/grayswan.mdx

[akshaydeo]

Merge activity

• Jul 24, 7:34 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 24, 7:34 AM UTC: @akshaydeo merged this pull request with Graphite.