…Redis

The provider now narrows on the discrete enrollment fields instead of
leaving every filter to the database, which applied them to the already
truncated candidate list. A broad query with country=US returned 85 rows
out of 7,698 real matches; measured on 5,000 seeded partners, filtering
inside the query takes that from 20% to 100% of the true set.

Metrics stay out on purpose: they move on every click and conversion, so
indexing them would make the document churn continuously.

Namespace moves to v3 — the new attributes do not exist on v2 rows.

…ch' into feature/partner-full-text-search-rollout

package.json moved back to ^1.35.3 without regenerating the lockfile, so
CI's frozen-lockfile install failed before building. The resolved version
is unchanged — 1.38.2 satisfies the range — so only the specifier moves.

Both described a two-provider world that this branch removed, and the first
also described the wrong filtering model.

types.ts said filters run after the truncation and called indexing them "out
of scope here" — but that is what this branch implemented, and turbopuffer.ts
says the opposite three files away. Anyone reading the constant would have
understood the model backwards. It now names what the provider filters before
the cut (status, group, country, tags) and what the database filters after it
(tenant, explicit partner IDs, referral, metric ranges), matching the schema
and the databaseOnlyFilters list.

The 999 ceiling is described as inherited from the removed Redis provider
rather than derived, since nothing enforces it now. The floor beyond it is
framed as the accepted trade it is, with what raising it would cost on every
query, rather than as a known limitation inviting a fix.

shared.ts loses the Redis-versus-Turbopuffer packaging explanation and the
"both providers store" phrasing.

…full-text-search-rollout

# Conflicts:
#	apps/web/lib/api/partners/search/providers/shared.ts
#	apps/web/lib/api/partners/search/providers/turbopuffer.ts
#	apps/web/lib/api/partners/search/types.ts
#	apps/web/scripts/dev/seed-100k-partners.ts

The note carried the Redis provider's history and a long defense of the
trade-off. Keeps the filter order, the lower-bound behavior, and what raising
the ceiling costs.

…full-text-search-rollout

debug-partner-search kept its own copy of the namespace name, which stayed on
partner-search-v2 when the filterable-attribute change bumped the provider to
v3. Its candidate search went to v3 through the provider while its indexed-text
lookup went to v2, so --searchOnly reported empty names and zero tokens instead
of failing.

Export the constant and import it, so the two cannot drift again.

…full-text-search-rollout

The candidate path selects the database route on the trimmed value, so
a pasted " pn_… " or " user@x.com " reached the exact match untrimmed
and found nothing.

The digit sniff could classify a permanent failure as transient when an
ID or count in the message contained 500 or 429. Typed APIError carries
the status; message matching remains only for non-SDK network errors.

…full-text-search-rollout

…full-text-search-rollout

# Conflicts:
#	apps/web/lib/api/partners/search/providers/turbopuffer.ts