ENG-2108 Add ranked search to QueryEngine with a vault-iteration fallback

[trangdoan982]

Scope check

• Ran $scope-check against ENG-2108 and the final diff.
• Scope beyond Done When: None.

Mapping

One file, one concern. Three deviations from the ticket's literal wording, all narrowing rather than expanding: createScorer was dropped as a meaningless one-line wrapper over prepareFuzzySearch; the Scorer type and the scorer? injection parameter were dropped as unused indirection, so prepareFuzzySearch is called directly; and filterCandidatesByNodeTypeIds is exported instead, because the ticket requires callers to memoize the filtered array — which is only possible if the filter is callable on its own. No new dependencies, no migrations, no unrelated refactors.

What this does

Adds the search seam for the Obsidian advanced node search panel (F1 of Advanced Node Search (Obsidian)). No UI — the panel is #1285, stacked on this.

QueryEngine.ts:

Export	Runs	Purpose
DiscourseNodeCandidate, RankedDiscourseNode	—	types
getDiscourseNodeCandidates()	once per open	every DG node as { file, title, nodeTypeId }
filterCandidatesByNodeTypeIds(...)	on filter change	node-type narrowing, OR across types
rankDiscourseNodesByTitle({...})	per keystroke	filter, score, sort

Three decisions worth reviewing

Datacore first, vault iteration as fallback — via delegation, so it is not visible in this diff. The call chain:

getDiscourseNodeCandidates()          ← new here
  └─ getFilesWithNodeTypeId()         ← existing, unchanged, so not in the diff
       ├─ Datacore installed  → `@page and exists(nodeTypeId)`
       └─ absent or throws    → fallbackGetFilesWithNodeTypeId()  (vault iteration)

Reusing that method rather than writing a second fallback here is why NF3 holds for free.

Verification

check-types clean, eslint 0 problems on the changed file.

The reviewable demo is #1285, stacked on this branch: https://www.loom.com/share/877db7d2de834548a81bca1750bbbecb

🤖 Generated with Claude Code

[linear-code]

ENG-2108

[supabase]

This pull request has been ignored for the connected project zytfjzqyijgagqxrzbmz because there are no changes detected in packages/database/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
discourse-graph	Skipped		Aug 9, 2026 5:28pm

[devin-ai-integration]

Devin Review found 1 potential issue.

View 1 additional finding in Devin Review.