vendor-abstraction

name	vendor-abstraction
description	Guardrails for edits to core/abstraction/vendor-abstraction.js that preserve vendor isolation, mappings, fallback selection, and stable client-facing schemas. Use when adding/removing vendors, operations, or schema fields.

Vendor Abstraction Guardian

Purpose & Scope

Apply this skill when modifying core/abstraction/vendor-abstraction.js.

The Vendor Abstraction Layer provides:

• Isolation between client requests and vendor-specific implementations
• Schema validation for client inputs
• Transform functions to convert client input to vendor format
• Multi-vendor support with fallback capabilities
• Category-based service organization (payment, banking, infrastructure)

Non-Negotiables (Never Do)

Schema Isolation

• Never expose vendor-specific field names in client schema.
• Never let vendor response leak directly to client without transformation.
• Never add vendor-specific validation in client schema.

Vendor Selection

• Never hardcode vendor selection logic in business code.
• Never remove a vendor without 30-day deprecation notice.
• Never make vendor selection observable from client input.
• Never expose vendor identifiers in client-facing responses.

Schema Stability

• Never add required fields to existing client schemas.
• Never remove or rename fields from existing client schemas.
• Never change field types in existing client schemas.

Category Management

• Never remove a category without migrating all operations.
• Never merge categories.
• Never duplicate operations across categories.

Required Patterns (Must Follow)

Client Schema Definition