fix(search): restore cross-field Cmd-K matches

[waleedlatif1]

Summary

Follow-up to #6192, fixing a regression Cursor Bugbot caught there after it merged.

#6192 moved folder paths out of the primary fuzzy haystack into filterAndCap's toExtra parameter, so an exact name match could no longer be outranked by a folder that happened to fuzzy-match. That ranking fix was right, but scoreItem matches the name or the secondary text and never the two together — so a query spanning both stopped matching at all:

• "leads emea" for a Leads table in the EMEA folder → no results
• This affected workflows and files too, which had the concatenating behavior before fix(search): disambiguate tables and knowledge bases by folder #6192

Fix

scoreItem now falls back to matching the two fields joined, but only when neither matches alone. Ordering matters: the joined attempt runs last so a secondary-text hit still cannot masquerade as a name hit, preserving the ranking #6192 established.

Positions from the joined match don't index into either field — safe here only because filterAndSort scores with them and discards them. Called that out in the TSDoc so nobody later feeds them to a highlighter.

Type of Change

• Bug fix

Testing

• 4 new tests covering cross-field match, name-beats-secondary ranking, secondary-only match, and non-match
• Mutation-checked: reverting the fix turns the cross-field test red
• tsc and bun run lint:check pass

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 2, 2026 7:11am

[cursor]

PR Summary

Low Risk
Localized change to search-modal fuzzy scoring with regression tests; no auth, data, or API surface changes.

Overview
Restores Cmd-K search when a query spans the item name and folder path (e.g. leads emea for a Leads table under EMEA), which broke after name and secondary text were scored separately.

In scoreItem, after name-only and secondary-only fuzzyMatch attempts fail, it now falls back to matching name + extra joined—only as a last step so name hits still outrank folder-only hits. TSDoc notes that match positions from the joined string must not be used for highlighting.

Adds four tests for cross-field match, name-over-secondary ranking, secondary-only match, and no match.

^{Reviewed by Cursor Bugbot for commit f4683a4. Configure here.}

[greptile-apps]

Greptile Summary

The PR restores Cmd-K queries that span an item's primary name and secondary searchable text while retaining the existing preference for direct name matches.

• Adds a final fuzzy-match attempt over the name and secondary text joined together.
• Documents why joined-match positions must not be used for highlighting.
• Adds regression coverage for cross-field matching, ranking, secondary-only matching, and non-matches.

Confidence Score: 5/5

The PR appears safe to merge, with the intended cross-field search behavior restored without weakening direct-name ranking.

The joined fallback runs only after both individual fields fail, absent secondary values remain protected by the existing guard, and match positions are discarded by the sole scoring consumer.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/w/components/sidebar/components/search-modal/utils.ts	Adds a guarded joined-field fallback after name-only and secondary-only matching; no actionable defect was identified.
apps/sim/app/workspace/[workspaceId]/w/components/sidebar/components/search-modal/utils.test.ts	Adds focused regression tests covering the intended cross-field behavior and preserved ranking semantics.

_{Reviews (1): Last reviewed commit: "fix(search): restore cross-field Cmd-K m..." | Re-trigger Greptile}