feat(search): wire idx_listing_fulltext for title+description keyword search

[abdout]

Independent of every other PR in flight. Branched off main.

What

Turns the orphan idx_listing_fulltext GIN index — created in 20250922091446_add_performance_indexes/migration.sql — into a real keyword-search capability. Until now the index was paying for writes (every INSERT INTO "Listing" touched it) without contributing a single read.

-- The index that's been sitting unused since v1.0
CREATE INDEX IF NOT EXISTS idx_listing_fulltext ON "Listing" USING GIN (
  to_tsvector('english', COALESCE(title, '') || ' ' || COALESCE(description, ''))
);

How

SearchFilters gains an optional query field. When set, cachedListingSearch runs a small $queryRaw against the existing index to get matching listing IDs, then intersects the regular Prisma where-clause with id IN (...):

if (f.query) {
  const ids = await getFullTextMatchingIds(f.query);
  if (ids.length === 0) return [];
  where.id = { in: ids };
}
return db.listing.findMany({ where, ... });

Two-step instead of one big $queryRaw for the whole search because the rest of the where-clause (price ranges, amenity arrays, date-overlap subquery) is much cleaner through the Prisma builder. Keeping it typed is worth more than collapsing the round trips at this scale.

URL surface

/{lang}/listings?q=beach              ← short form, conventional
/{lang}/listings?query=beach          ← alias for clarity
/{lang}/listings?q=villa&priceMax=200 ← composes with all existing filters

The page also adds a quoted-keyword chip to the search summary so users can see why a result set looks unfamiliar:

"beach" · Khartoum · 2 guests · 2026-05-15 - 2026-05-22

What this does NOT do

• No UI input yet. The URL contract is in place; a search box in big-search.tsx can wire to it as a follow-up. Server is forward-compatible.
• No synonyms / language switching. The index was built with the 'english' dictionary so we keep that. Arabic content in title/description will tokenize on whitespace — good enough for now; a separate Arabic config is a future migration.
• No re-indexing required. The GIN index already exists in production (verified by reading the migration history); this PR just starts using it.

Behavior matrix

query value	Result
undefined / not set	Today's exact path — no $queryRaw, no id IN (...) filter
"" or " "	Validation error (Zod .trim().min(1)) — searchListings returns { success: false } rather than silently matching everything
"beach"	plainto_tsquery('english', 'beach') — index lookup, IDs intersected with filters
"luxury beach"	Parses as 'luxury' & 'beach' — both terms required
Match returns []	Short-circuits before findMany
Extension/index missing	Helper catches → returns [] → empty result rather than 5xx

Validation

pnpm typecheck	✅ exit 0
pnpm vitest run	✅ 836 / 836 (added 3 tests for the new path)

Test plan after deploy

# 1. Existing search untouched
curl -s 'https://mk.databayt.org/en/listings' | head

# 2. Keyword search returns only matching titles/descriptions
curl -s 'https://mk.databayt.org/en/listings?q=beach' | head

# 3. Two-word query enforces AND
curl -s 'https://mk.databayt.org/en/listings?q=luxury+villa' | head

# 4. Empty match short-circuits
curl -s 'https://mk.databayt.org/en/listings?q=zzznever' | head

Diff stat

src/lib/schemas/search-schema.ts     | +11   query field added to SearchFilters + zod
src/lib/actions/search-actions.ts    | +51   getFullTextMatchingIds + branch in search/count
src/app/[lang]/listings/page.tsx     | +20   URL param wiring + summary chip
tests/actions/search-actions.test.ts | +43   3 new tests

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
mkan	Ready	Preview, Comment	May 10, 2026 6:08am