fix: bedrock outputAssessments type correction

[TejasGhatte]

Summary

Fixes a crash introduced in Bifrost 1.4.6 where Bedrock Converse calls with trace: enabled would always return an InternalServerError. The root cause was a type mismatch: BedrockGuardrailTrace.OutputAssessments was typed as []BedrockGuardrailAssessment (a slice), but Bedrock returns outputAssessments as map[guardrailId][]Assessment (a map keyed by guardrail ID). This caused JSON unmarshalling to crash on every guardrailed Converse call that reached the model and produced output.

Changes

• Corrected BedrockGuardrailTrace.OutputAssessments from []BedrockGuardrailAssessment to map[string][]BedrockGuardrailAssessment to match the actual Bedrock API shape
• Corrected BedrockGuardrailTrace.InputAssessment from map[string]interface{} to map[string]BedrockGuardrailAssessment for type safety
• Unified the struct to a single shape covering both Converse and ConverseStream paths, removing the previously incorrect split between "streaming" and "non-streaming" field sets
• Expanded BedrockGuardrailAssessment with the full set of fields returned by Bedrock, including AppliedGuardrailDetails, AutomatedReasoningPolicy, ContextualGroundingPolicy, and InvocationMetrics
• Added supporting types: BedrockGuardrailAppliedDetails, BedrockGuardrailAutomatedReasoningPolicy, BedrockGuardrailContextualGroundingPolicy, BedrockGuardrailContextualGroundingFilter, BedrockGuardrailInvocationMetrics, BedrockGuardrailCoverage, BedrockGuardrailCoverageCount, and BedrockGuardrailUsage
• Added a regression test (test_56) to the Bedrock integration suite asserting outputAssessments is a map, not a list
• Added regression tests (test_31, test_32) to the LangChain integration suite covering both non-streaming and streaming paths
• Added a Postman/Newman e2e collection test case for the guardrailConfig + trace path that validates outputAssessments shape

Note: A benign prompt is intentionally used in all regression tests. A blocked prompt never reaches the model, so outputAssessments would be absent in the trace — masking the type-mismatch bug entirely.

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

# Core
go test ./core/providers/bedrock/...

# Integration tests (requires AWS credentials and a configured guardrail)
export BEDROCK_GUARDRAIL_IDENTIFIER=<your-guardrail-id>
export BEDROCK_GUARDRAIL_VERSION=DRAFT  # or a pinned version

cd tests/integrations/python
pytest tests/test_bedrock.py::TestBedrockConverse::test_56_outputAssessments_is_map -v
pytest tests/test_langchain.py::TestLangChainBedrock::test_31_bedrock_guardrail_outputAssessments_is_map -v
pytest tests/test_langchain.py::TestLangChainBedrock::test_32_bedrock_guardrail_streaming_outputAssessments_is_map -v

Set the following environment variables to enable guardrail tests:

Variable	Description
BEDROCK_GUARDRAIL_IDENTIFIER	The guardrail ID to use for trace regression tests
BEDROCK_GUARDRAIL_VERSION	Guardrail version (defaults to DRAFT)

Breaking changes

• Yes
• No

Security considerations

No new auth, secrets, or PII handling introduced. The fix only corrects the Go type used to deserialise guardrail trace data returned by AWS Bedrock.

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]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 890832a9-d668-4350-82d4-5e3f6a4c9d61

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-03-fix_type_correction_bedrock_outputassessments

---

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

[TejasGhatte]

• fix: bedrock outputAssessments type correction #4028 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

tejas ghatte seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[akshaydeo]

Merge activity

• Jun 3, 3:31 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 3, 3:31 PM UTC: @akshaydeo merged this pull request with Graphite.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Bifrost	🟡 Building	–	Jun 3, 2026, 3:28 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.