AI pricebook resolver: fall back to CRM mappings

Plaid stores pricebook currency/type in crmOpportunityMappings, not selectorTags — the resolver now reads both.

1. Why this exists

The Dealops 2 AI quoting pipeline calls resolvePricebookFromTerms to turn a user's term selection (pricebook name + currency) into a fully-formed LoadedPricebook with currency and pricebookType. Today the resolver re-fetches the raw Prisma row and reads those two values exclusively from selectorTags.

Plaid's pricebooks don't populate selectorTags — their selector metadata is encoded as crmOpportunityMappings with named fields like pricebook and quoteCurrency. The resolver therefore failed loudly for every Plaid AI quote, even when the matching pricebook was selected correctly upstream.

2. Before / after

const tags = raw.selectorTags ?? {};
const currency =
  typeof tags.currency === 'string'
    ? tags.currency : null;
const pricebookType =
  typeof tags.pricebookType === 'string'
    ? tags.pricebookType : null;

if (!currency || !pricebookType) {
  throw new Error(
    `selectorTags missing required fields...`
  );
}

const currency = normalizeCurrency(
  getSelectorTagString(tags, 'currency') ??
    getEqualsMappingString(
      result.pricebook.crmOpportunityMappings,
      'quoteCurrency',
    ),
);
const pricebookType = normalizePricebookType(
  getSelectorTagString(tags, 'pricebookType') ??
    getEqualsMappingString(
      result.pricebook.crmOpportunityMappings,
      'pricebook',
    ),
);

3. How resolution flows

For each of currency and pricebookType, the resolver now walks a two-step chain before giving up:

4. The mapping shape it parses

Plaid's crmOpportunityMappings is an array of objects. The resolver only trusts entries with operator "equals" and a non-empty string value:

[
  { displayName: 'Pricebook', name: 'pricebook',
    operator: 'equals', dataType: 'string', value: 'CPQ' },
  { displayName: 'Currency', name: 'quoteCurrency',
    operator: 'equals', dataType: 'string', value: 'USD' }
]

The lookup is name-keyed, so the mapping for currency resolution uses key quoteCurrency and the mapping for pricebookType uses key pricebook. Any other operator (e.g. in, notEquals) or non-string value is ignored — the resolver only handles the single-value equality case.

5. Test coverage added

6. What it doesn't change

7. Risks & notes