fix(ui): replace remaining client-side connection filtering with server-side

[viktormarinho]

Summary

• Replace useConnections() + getConnectionSlug() lookups with useConnections({ filters: [{ column: "app_name", value: appSlug }] }) in connection detail, virtual-mcp detail, workflow hooks, and collection detail
• Use binding: "WORKFLOW" for workflow binding connection hook
• Use binding: "LLM" in private-registry plugin components (monitor-configuration, registry-settings)
• Use server-side binding filtering in binding-selector and mcp-configuration-form for string binding types
• Add includeVirtual option to tool-set-selector

Stack

PR 5/5 — Remaining filters (base: PR 4)

Test plan

• Verify connection detail page resolves connections by app_name correctly
• Verify workflow detail pages still find their parent connections
• Verify binding selector dropdowns show correct filtered connections
• Verify LLM connection dropdowns in private-registry plugin work

🤖 Generated with Claude Code

---

Summary by cubic

Replaced remaining client-side connection filtering with server-side useConnections queries by app_name or binding across connection, virtual MCP, workflow, collection, and private‑registry views to reduce over‑fetching and keep results consistent. Removed Binder‑based filtering and standardized WORKFLOW/LLM lookups.

• Refactors
  • Use useConnections({ filters: [{ column: "app_name", value: appSlug }] }) in connection, virtual MCP, workflow, and collection views; remove getConnectionSlug() lookups.
  • Use useConnections({ binding: "WORKFLOW" }) in workflow hooks and useConnections({ binding: "LLM" }) in private‑registry components.
  • Update binding-selector and MCP configuration form to use server‑side binding filtering; drop Binder support, fall back to app_name for unknown registry types, and pass bindingName from plugins (project-plugins-form).
  • Remove useBindingConnections and related tests; in connection settings, detect MCP by checking for MCP_CONFIGURATION* tools.
  • In tool-set-selector, pass includeVirtual: !!excludeVirtualMcpId and filter out only the excluded virtual connection.

^{Written for commit a340e12. Summary will update on new commits.}

[github-actions]

🧪 Benchmark

Should we run the Virtual MCP strategy benchmark for this PR?

React with 👍 to run the benchmark.

Reaction	Action
👍	Run quick benchmark (10 & 128 tools)

Benchmark will run on the next push after you react.

[github-actions]

Release Options

Suggested: Patch (2.202.4) — based on fix: prefix

React with an emoji to override the release type:

Reaction	Type	Next Version
👍	Prerelease	2.202.4-alpha.1
🎉	Patch	2.202.4
❤️	Minor	2.203.0
🚀	Major	3.0.0

Current version: 2.202.3

Note: If multiple reactions exist, the smallest bump wins. If no reactions, the suggested bump is used (default: minor).

[cubic-dev-ai]

3 issues found across 10 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/mesh/src/web/components/binding-selector.tsx">

<violation number="1" location="apps/mesh/src/web/components/binding-selector.tsx:68">
P2: Using the server-filtered query as `allConnections` breaks the “keep selected connection even if filtered out” fallback, since the selected item may no longer be present in the source list.</violation>
</file>

<file name="apps/mesh/src/web/routes/orgs/collection-detail.tsx">

<violation number="1" location="apps/mesh/src/web/routes/orgs/collection-detail.tsx:54">
P1: Filtering connections with `app_name = params.appSlug` mismatches how `$appSlug` is generated (`getConnectionSlug`), so valid detail routes can fail to resolve their connection.</violation>
</file>

<file name="apps/mesh/src/web/components/details/virtual-mcp/index.tsx">

<violation number="1" location="apps/mesh/src/web/components/details/virtual-mcp/index.tsx:144">
P1: Sibling instance matching no longer enforces canonical slug equality, so connections without `app_name` can incorrectly treat all non-virtual connections as siblings.

(Based on your team's feedback about using `getConnectionSlug()` as the canonical sibling identifier.) [FEEDBACK_USED]</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}