card-identitylisted

# Card Identity ## Purpose Centralized card-name resolution used by all commands in the card suite. Every user-facing command should call this logic as step 1 before doing any research. ## Resolution Steps 1. **Normalize input** — strip extra whitespace, fix common abbreviations (e.g., "CSP" → "Chase Sapphire Preferred", "Amex" → "American Express"). 2. **Parse components** — extract issuer, card family, and card variant separately when possible. 3. **Check issuer scope** — verify the issuer is in the approved list from [../card-shared/source-policy.yaml](../card-shared/source-policy.yaml). If not, return a short failure: "This card is not from a supported issuer." 4. **Resolve variant** — if the input maps to exactly one variant, proceed with confident match. If multiple variants are plausible, follow the ambiguity rules below. ## Business vs Personal - Both personal and business credit cards are supported. - If the user specifies "business" or "biz", resolve to the business variant. - If a card name exists in both personal and business versions and the user doesn't specify, treat it as **ambiguous** — return a numbered choice list with both variants. - Common business indicators: "business", "biz", "Business Platinum", "Ink", "Spark", etc. ## Ambiguity Handling - If the input maps to 2+ plausible variants (e.g., "Chase Sapphire" → Preferred or Reserve, or "Amex Gold" → personal or business): - Return a **numbered choice list** and stop. Do not guess. - Format: o