test case fixes for helm release

[akshaydeo]

Summary

This PR adds five new agent skills to the .agents/skills/ directory to enhance the development workflow for the Bifrost project. These skills provide automated assistance for common development tasks including changelog generation, documentation writing, E2E testing, issue investigation, and PR comment resolution.

Changes

• changelog-writer: Automates changelog generation by reading git history, bumping module versions following the core→framework→plugins→transport hierarchy, and writing both enterprise-style and per-module changelog files
• docs-writer: Creates and updates Mintlify MDX documentation by exploring the full codebase (UI, Go backend, config schema), validating config.json examples, and following established documentation conventions
• e2e-test: Manages Playwright E2E tests with capabilities for writing new tests, debugging failures, auditing test correctness, and auto-syncing tests with UI changes
• investigate-issue: Provides comprehensive GitHub issue analysis by fetching issue details, analyzing the codebase, researching documentation via Context7, and presenting actionable implementation plans
• resolve-pr-comments: Offers interactive PR comment resolution workflow with systematic addressing of review feedback and proper reply handling

Each skill includes detailed documentation with usage patterns, workflow steps, mandatory rules, error handling, and project-specific conventions.

Type of change

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

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (Next.js)
• Docs

How to test

These are agent skill definitions that will be used by AI agents in the development workflow. To validate:

1. Verify skill structure:

# Check that all skills have proper frontmatter and structure
for skill in .agents/skills/*/SKILL.md; do
  echo "Checking $skill..."
  head -10 "$skill" | grep -E "^(name|description|allowed-tools):"
done

2. Validate markdown formatting:

# Ensure proper markdown syntax
markdownlint .agents/skills/*/SKILL.md

3. Check references to project structure:

# Verify that referenced directories exist
grep -r "ui/app/workspace" .agents/skills/
grep -r "core/internal/llmtests" .agents/skills/
grep -r "tests/e2e/" .agents/skills/

The skills reference existing project conventions and file structures, so they should align with the current codebase organization.

Screenshots/Recordings

N/A - These are documentation files for agent skills.

Breaking changes

• Yes
• No

This adds new agent capabilities but doesn't break existing functionality. The skills are additive and follow established project patterns.

Related issues

These skills support the general development workflow and don't address specific GitHub issues, but they will help with:

• Automated changelog generation for releases
• Consistent documentation creation and updates
• Improved E2E test coverage and maintenance
• Systematic issue investigation and resolution
• Streamlined PR review processes

Security considerations

The skills use standard development tools (git, gh CLI, grep, etc.) and don't introduce new security vectors. They follow read-only patterns for codebase analysis and require explicit user approval for any modifications.

Checklist

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

[coderabbitai]

Warning

Rate limit exceeded

@akshaydeo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 55 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 5 minutes and 55 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 19b0cbd7-222b-4ba0-a338-1d802fe4db02

📥 Commits

Reviewing files that changed from the base of the PR and between 254e41e and fd03e33.

📒 Files selected for processing (1)

• .github/workflows/scripts/validate-helm-config-fields.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 04-15-test_case_fixes_for_helm_release

---

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

[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.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[akshaydeo]

• test case fixes for helm release #2738 👈 (View in Graphite)
• main

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

[github-actions]

🧪 Test Suite Available

This PR can be tested by a repository admin.

Run tests for PR #2738

[akshaydeo]

Merge activity

• Apr 15, 3:05 PM UTC: A user started a stack merge that includes this pull request via Graphite.

[greptile-apps]

Confidence Score: 5/5

Safe to merge — all findings are P2 style issues that do not affect test correctness or CI outcomes.

The logic changes (field renames, new nested compat block, trace_type value, SAML→SCIM) are internally consistent and the corresponding assertions are updated correctly. The only remaining finding is a cosmetic stale label in the section header echo output, which does not affect whether tests pass or fail.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/scripts/validate-helm-config-fields.sh	Test fixtures updated: enableLitellmFallbacks replaced by a nested compat block, trace_type changed to genai_extension, and SAML sections renamed to SCIM with an added apiToken field. Section 8 header/echo still reference "SAML" after the rename.

Comments Outside Diff (1)

1. .github/workflows/scripts/validate-helm-config-fields.sh, line 826-829 (link)

   Stale "SAML" references in section header

   The section title comment and the echo banner still say "SAML" while the test body was fully migrated to SCIM. CI output will still print "SAML" even though no SAML tests exist any more, which is confusing.

_{Reviews (1): Last reviewed commit: "test case fixes for helm release" | Re-trigger Greptile}