feat(helm): add complexity analyzer config values support

[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

Summary by CodeRabbit

• New Features

  • Opt-in Helm support to seed complexity analyzer tier thresholds and keyword groups (defaults apply when omitted or null).
  • Helm-provided analyzer settings are reapplied on restart; runtime UI/API edits hot-reload until restart.
  • Helm values now validated against a stricter schema to ensure required thresholds and keyword lists.

• Documentation

  • Added a Complexity Router Configuration section with examples and guidance.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Adds Helm-configurable complexity analyzer settings: JSON schema for validation, values placeholder and template rendering into generated config.json, and documentation explaining defaults and runtime behavior.

Changes

Complexity Analyzer Configuration Support

Layer / File(s)	Summary
Schema validation for complexity analyzer config helm-charts/bifrost/values.schema.json	New bifrost.governance.complexityAnalyzerConfig schema enforces required tier_boundaries numeric thresholds and required keyword arrays (code_keywords, reasoning_keywords, technical_keywords, simple_keywords) with strict additionalProperties: false.
Helm values and template rendering helm-charts/bifrost/values.yaml, helm-charts/bifrost/templates/_helpers.tpl, helm-charts/bifrost/README.md	Default complexityAnalyzerConfig value set to null with commented example. Template conditionally adds complexity_analyzer_config to governance block when Helm values are provided; emission guard updated to ensure governance is emitted when this is the only populated governance field. Changelog and spacing updated.
Configuration documentation docs/deployment-guides/helm/governance.mdx	Documents how bifrost.governance.complexityAnalyzerConfig maps to governance.complexity_analyzer_config in generated config.json, behavior when omitted or null, restart vs hot-reload semantics, and includes example YAML for tier boundaries and keyword lists.

Sequence Diagram(s):

sequenceDiagram
  participant Operator as Operator
  participant Helm as Helm CLI
  participant Template as _helpers.tpl
  participant Config as generated config.json
  Operator->>Helm: supply `bifrost.governance.complexityAnalyzerConfig` values
  Helm->>Template: render templates with values
  Template->>Config: emit `governance.complexity_analyzer_config` into config.json

Loading

Estimated code review effort:
🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers:

• danpiths
• akshaydeo

"I hopped through charts and values true,
seeded tiers and keywords just for you.
Schema guards the gates with care,
templates render settings there.
A rabbit's stamp on config flair. 🐰"

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is a blank template with no actual content filled in; all sections remain as placeholder text with no implementation details, changes explanation, type selection, affected areas, testing steps, or related issues linked.	Complete the PR description by filling in the Summary, Changes, Type of change, Affected areas, How to test, Breaking changes, Related issues, and Security considerations sections with actual details relevant to this complexity analyzer configuration addition.
Linked Issues check	⚠️ Warning	The linked issue #123 (Files API Support) concerns OpenAI/Anthropic file uploads for RAG workflows, which is unrelated to the Helm complexity analyzer configuration changes in this PR.	Link the correct issue(s) related to complexity analyzer configuration support, or clarify the relationship between this Helm change and the Files API requirements.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'feat(helm): add complexity analyzer config values support' directly and clearly summarizes the main change of adding Helm configuration support for complexity analyzer settings.
Out of Scope Changes check	✅ Passed	All changes (Helm templates, values schema, values defaults, documentation) are directly in-scope for adding complexity analyzer config support; no unrelated modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-01-feat_helm_add_complexity_analyzer_config_values_support

---

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

[Madhuvod]

• feat(helm): add complexity analyzer config values support #3948 👈 (View in Graphite)
• docs for complexity router and openapi reference #3716
• feat(ui): add complexity router config UI and CEL support #3715
• complexity router : add complexity analyzer config DB and API changes #3712
• feat: complexity router : adds complexity_tier CEL routing #3711
• feat: enforce routing allowlist in core and propagate VK provider constraints via context key #3936 : 1 other dependent PR (#4014 )
• docs: document PreRequestHook routing phase, per-request vs per-attempt semantics, and updated plugin sequencing #3935
• refactor: move model-catalog provider resolution into a modelcatalogresolver PreRequestHook plugin #3934
• refactor: migrate governance routing from HTTPTransportPreHook to PreRequestHook #3933
• feat: add PreRequestHook to LLMPlugin interface as a once-per-request routing phase before PreLLMHook #3932
• dev

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

[Madhuvod]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[greptile-apps]

Confidence Score: 5/5

Safe to merge; all Helm changes are opt-in and backwards-compatible with existing installs.

The Helm template change is correctly guarded by a nil check, the inline schema faithfully mirrors the canonical config schema, and null defaults mean no existing deployment is affected. The only notable items are an unrelated binary asset and a pre-existing schema gap (threshold ordering) that is already caught by Go runtime validation — neither is a functional regression.

ui/public/images/microsoft.png — appears to be an accidental inclusion unrelated to this feature.

Important Files Changed

Filename	Overview
helm-charts/bifrost/templates/_helpers.tpl	Adds complexity_analyzer_config block to governance config rendering; correctly guarded by an if-nil check so existing installs are unaffected.
helm-charts/bifrost/values.schema.json	Inline schema for complexityAnalyzerConfig matches canonical transports/config.schema.json structure with correct minItems/minLength guards; tier boundary ordering constraint is not enforced (pre-existing gap in the source schema too).
helm-charts/bifrost/values.yaml	Adds complexityAnalyzerConfig defaulting to null with commented-out example; opt-in and backwards-compatible.
docs/deployment-guides/helm/governance.mdx	New Complexity Router Configuration section accurately describes opt-in Helm seeding and hot-reload semantics; examples match the schema.
helm-charts/bifrost/README.md	Changelog entry for upcoming 2.1.23 correctly describes the new complexityAnalyzerConfig field and its opt-in behaviour.
ui/public/images/microsoft.png	Unrelated binary asset added; no changed file in this PR references it, suggesting an accidental inclusion from a separate feature branch.

_{Reviews (15): Last reviewed commit: "feat(helm): add complexity analyzer conf..." | Re-trigger Greptile}

[Madhuvod]

@coderabbitai did you review?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh pr view 3948 --repo maximhq/bifrost --json reviews,comments,state,title

Length of output: 23954

---

---

@Madhuvod The initial auto-review was skipped because auto reviews are disabled on non-default base branches for this repository. When you triggered @coderabbitai review, since CodeRabbit is an incremental system and the commits were already processed during the walkthrough generation, it didn't produce additional inline review comments.

Let me kick off a full review of all the changes now.

✅ Actions performed

Full review triggered.

[coderabbitai]

🧹 Nitpick comments (1)

docs/deployment-guides/helm/governance.mdx (1)

359-385: ⚡ Quick win

Add required Mintlify tabs and a schema-aligned config.json example.

This new section should include Web UI / API / config.json tabs, and the config.json tab should show governance.complexity_analyzer_config with schema-valid tier_boundaries and keywords.

Suggested structure

+<Tabs>
+  <Tab title="Web UI">
+    Configure complexity analyzer settings in the Governance UI.
+  </Tab>
+  <Tab title="API">
+    Use the governance config API to set `complexity_analyzer_config`.
+  </Tab>
+  <Tab title="config.json">
+```json
+{
+  "governance": {
+    "complexity_analyzer_config": {
+      "tier_boundaries": {
+        "simple_medium": 0.15,
+        "medium_complex": 0.35,
+        "complex_reasoning": 0.60
+      },
+      "keywords": {
+        "code_keywords": ["function", "class", "api", "debug", "deploy"],
+        "reasoning_keywords": ["step by step", "explain why", "tradeoffs", "root cause analysis"],
+        "technical_keywords": ["architecture", "kubernetes", "latency", "authentication"],
+        "simple_keywords": ["hello", "hi", "thanks", "what is", "define"]
+      }
+    }
+  }
+}
+```
+  </Tab>
+</Tabs>

As per coding guidelines docs/**/*.mdx: Mintlify MDX documentation must have Web UI / API / config.json tabs; validate config.json examples against transports/config.schema.json.

🤖 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/deployment-guides/helm/governance.mdx` around lines 359 - 385, Add
Mintlify tabs "Web UI", "API", and "config.json" to the Complexity Router
Configuration section and replace the inline YAML-only example with the tabbed
UI; in the config.json tab include a JSON example that sets
governance.complexity_analyzer_config with schema-aligned objects:
tier_boundaries containing simple_medium, medium_complex, complex_reasoning as
numeric values (e.g., 0.15, 0.35, 0.60) and keywords containing arrays for
code_keywords, reasoning_keywords, technical_keywords, and simple_keywords;
ensure the JSON keys exactly match complexityAnalyzerConfig /
governance.complexity_analyzer_config and that values conform to
transports/config.schema.json (types and structure) so the example validates.

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

Nitpick comments:
In `@docs/deployment-guides/helm/governance.mdx`:
- Around line 359-385: Add Mintlify tabs "Web UI", "API", and "config.json" to
the Complexity Router Configuration section and replace the inline YAML-only
example with the tabbed UI; in the config.json tab include a JSON example that
sets governance.complexity_analyzer_config with schema-aligned objects:
tier_boundaries containing simple_medium, medium_complex, complex_reasoning as
numeric values (e.g., 0.15, 0.35, 0.60) and keywords containing arrays for
code_keywords, reasoning_keywords, technical_keywords, and simple_keywords;
ensure the JSON keys exactly match complexityAnalyzerConfig /
governance.complexity_analyzer_config and that values conform to
transports/config.schema.json (types and structure) so the example validates.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 23b48f86-c430-4c5d-ad3f-ca537419de23

📥 Commits

Reviewing files that changed from the base of the PR and between ccb6b3a and 8732199.

📒 Files selected for processing (4)

• docs/deployment-guides/helm/governance.mdx
• helm-charts/bifrost/templates/_helpers.tpl
• helm-charts/bifrost/values.schema.json
• helm-charts/bifrost/values.yaml

[akshaydeo]

Merge activity

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

The base branch was changed.