update complexity boundaries

[kohlivrinda]

Summary

Adjusts the complexity tier classification boundaries from 0.17/0.39 to 0.20/0.40 to better reflect the scoring distribution produced by the current keyword weight scale. The previous thresholds were causing borderline technical questions to land in SIMPLE when they should register a meaningful positive score, regardless of tier.

Changes

• simpleMediumBoundary raised from 0.17 → 0.20 and mediumComplexBoundary from 0.39 → 0.40 in the Go config and mirrored in the UI type definitions.
• Tests for TestAnalyze_SimpleKeywordDoesNotSuppressTechnicalSignals and TestAnalyze_AccessVsRefreshTokens were updated to reflect that these inputs now correctly score in SIMPLE under the new boundary — the assertions were relaxed from requiring a non-SIMPLE tier to requiring a positive score and a non-nil result, which is the meaningful invariant.
• The TestAnalyze_CustomTierBoundaries probe value was updated from 0.18 to 0.25 to sit clearly above the new 0.20 simple/medium boundary, keeping the default vs. custom boundary contrast valid.

Type of change

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

Affected areas

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

How to test

# Core/Transports
go test ./plugins/governance/complexity/...

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

Breaking changes

• Yes
• No

Related issues

Security considerations

None.

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 03525be8-4b1f-4f81-ba64-3c7e15ec86d3

📥 Commits

Reviewing files that changed from the base of the PR and between 2b1e8d4 and 486f0b2.

📒 Files selected for processing (3)

• plugins/governance/complexity/analyzer_test.go
• plugins/governance/complexity/config.go
• ui/lib/types/complexityRouter.ts

🚧 Files skipped from review as they are similar to previous changes (3)

• plugins/governance/complexity/analyzer_test.go
• ui/lib/types/complexityRouter.ts
• plugins/governance/complexity/config.go

---

📝 Walkthrough

Summary by CodeRabbit

• Updates

  • Adjusted default complexity score thresholds for SIMPLE, MEDIUM, and COMPLEX classifications.
  • Synchronized threshold behavior between complexity analysis and the user interface.
  • Complexity scores near classification boundaries may now receive a different tier.

• Tests

  • Updated boundary coverage for revised thresholds.
  • Strengthened technical-signal validation to confirm valid, positively scored analyses.
  • Improved coverage of classification behavior around updated thresholds.

Walkthrough

Complexity tier thresholds were updated in Go and TypeScript. Analyzer tests now use the revised boundary and validate positive scores for technical-signal cases without requiring specific tiers.

Changes

Complexity threshold retuning

Layer / File(s)	Summary
Update tier boundaries plugins/governance/complexity/config.go, ui/lib/types/complexityRouter.ts	Default simple-to-medium and medium-to-complex thresholds changed to 0.20 and 0.40.
Align analyzer tests plugins/governance/complexity/analyzer_test.go	The custom boundary test now uses 0.25. Two technical-signal tests now require successful analyses with positive scores instead of specific tiers.

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

Mergeability Score: ⚪ Minimal · up to 486f0

The PR adjusts complexity classification thresholds and keeps the corresponding tests and UI definitions aligned; no actionable merge-blocking risk remains beyond normal checks and review.

Possibly related PRs

• maximhq/bifrost#5494: Retunes the same complexity tier boundaries.
• maximhq/bifrost#5499: Modifies DEFAULT_TIER_BOUNDARIES in the same TypeScript file.
• maximhq/bifrost#5530: Applies the same 0.20 and 0.40 boundary changes across configuration and tests.

Suggested reviewers: akshaydeo, pratham-mishra04, madhuvod

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Description check	✅ Passed	The description explains the purpose, changes, affected areas, testing steps, breaking-change status, and security impact; optional sections are left empty.
Title check	✅ Passed	The title is concise and accurately identifies the main change to the complexity boundaries.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

---

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

[kohlivrinda]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• semantic router: incremental embedding + embed usage accounting #5896 : 2 dependent PRs (#5901 , #5924 )
• semantic router ui revamp #5865
• move complexity exemplars to configstore with backfill migration #5842
• feat(complexity): harness-aware complexity input extraction for cc and codex #5810
• server: export ObserveWarmupRoutingEmbedding for enterprise #5791
• weaviate + redis adapter fixes #5790
• semantic routing ui #5743
• semantic router: dimension probe + message history window #5748
• semantic cache: min similarity + fallback logging #5742
• smenatic router: budgeting+telemetry management #5686
• semantic routing #5: added semantic classifier for complexity router + handlers changes #5680
• semantic router #3: embedding executor #5656
• semantic router #2: semantic routing config #5655
• semantic router #1: add chromem backend #5628
• complexity : reducing keyword lists from 4 -> 3 lists #5602
• helm and docs changes #5530
• update complexity boundaries #5529 👈 (View in Graphite)
• expose tier/mechanism on every surface #5499
• structured logging #5497
• complexity tier merge #5494
• dev

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

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.