docs: add entity selector guidelines to AGENTS.md

[impoiler]

Summary

Adds developer guidance to AGENTS.md documenting the entity selector pattern, preventing future duplication of ad-hoc entity picker implementations across the UI.

Changes

• Documents the ui/components/entitySelectors/ directory as the canonical location for all entity pickers, covering available selectors (virtualKeySelector, teamSelector, customerSelector, userSelector, businessUnitSelector) and their three usage modes (single, multi, add)
• Explains the fallbackOption/fallbackOptions requirement for pre-selected rows to avoid raw UUID rendering before the popover fetches data
• Provides a step-by-step checklist for adding a new entity selector wrapper, including correct use of useEntitySelectorSearch(), useMemo for options stability, LabelResolver components, prop typing conventions, pagination defaults, and server-side search requirements
• Clarifies the boundary between entitySelector.tsx (shared behaviour only) and per-entity wrappers (entity-specific differences) and per-surface props
• Documents the OSS vs. enterprise placement rule: enterprise-only selectors live in bifrost-enterprise/ and are reached from OSS exclusively via runtime registries with empty fallbacks, never via direct imports

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

Review AGENTS.md to confirm the new section appears under the correct heading and that all code examples and rules are accurate against the existing ui/components/entitySelectors/ implementations.

Breaking changes

• Yes
• No

Related issues

Security considerations

None. This is documentation only.

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

Walkthrough

Updated AGENTS.md with UI guidance requiring shared entity selector components, fallback options for existing records, wrapper implementation practices, server-side search, and OSS-enterprise placement rules.

Changes

Entity selector guidance

Layer / File(s)	Summary
Document entity selector conventions AGENTS.md	Adds requirements for shared entity selectors, fallback options, new wrapper implementations, server-side filtering, label resolution, prop typing, and registry-based OSS access to enterprise selectors.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: akshaydeo

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR does not address Files API support; it only adds entity selector documentation, so it misses the linked issue requirements.	Implement the Files API work for POST /v1/files and provider file-upload support for fine-tuning, RAG, and larger context storage.
Out of Scope Changes check	⚠️ Warning	The change is unrelated to the Files API objective and consists only of AGENTS.md guidance about entity selectors.	Align the PR with issue #123 by adding Files API implementation work instead of unrelated documentation changes.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly matches the main change: adding entity selector guidelines to AGENTS.md.
Description check	✅ Passed	The description follows the template well and includes summary, changes, type, affected areas, testing, breaking changes, security, and checklist.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-29-feat_adds_instruction_to_agents.md_to_use_these_new_entity_selector_components

---

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

[impoiler]

• docs: add entity selector guidelines to AGENTS.md #5635 👈 (View in Graphite)
• feat: add limit/all params to rankings endpoints and use uncapped export snapshots in PDF/CSV #5625
• feat: add RankingLimit filter with all/limit query params to cap or remove ranking row limits #5624
• fix: show FullPageLoader on initial fetch to prevent empty-state flash in pricing overrides and model limits views #5623
• feat: replace full VirtualKeys preload with virtual_key_count on paginated customer list #5618
• feat: replace static list queries with async entity selectors for teams, customers, and virtual keys #5616
• refactor: extract shared VirtualKeySelector component and replace inline VK query logic across pricing, routing, MCP, and model-limit surfaces #5614
• dev

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

[coderabbitai]

Actionable comments posted: 1

🤖 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 `@AGENTS.md`:
- Line 842: Rephrase the instruction in AGENTS.md to say “Memoize the options
array with useMemo,” preserving the existing guidance and meaning.

🪄 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: c867b52c-1e06-4449-8340-d362c327c6ef

📥 Commits

Reviewing files that changed from the base of the PR and between 6afeaa4 and ccc3dcd.

📒 Files selected for processing (1)

• AGENTS.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Rephrase the useMemo instruction.

“useMemo the options array” is grammatically awkward. Use “Memoize the options array with useMemo” for clarity.

🧰 Tools

🪛 LanguageTool

[grammar] ~842-~842: Use a hyphen to join words.
Context: ... 2. useMemo the options array. Multi mode feeds it to react-select as `defaul...

(QB_NEW_EN_HYPHEN)

🤖 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 `@AGENTS.md` at line 842, Rephrase the instruction in AGENTS.md to say “Memoize
the options array with useMemo,” preserving the existing guidance and meaning.

Source: Linters/SAST tools

[akshaydeo]

Merge activity

• Jul 28, 8:46 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 28, 8:56 PM UTC: @akshaydeo merged this pull request with Graphite.