add-card-data-pipeline

To convert MTGJSON data, the card data pipeline loads raw inputs, builds oracle faces, applies synthesis rules, and exports typed card-data.json. You orchestrate changes across these paths to ensure end-to-end consistency.

MTG card data synthesis is the pipeline stage that processes parsed oracle faces into engine-ready outputs. You modify it when adding new fields or changing parser outputs, ensuring rules accuracy and validated exports.

To regenerate card-data.json after updates, run the oracle-gen data workflow. This workflow validates that your parsing and synthesis changes propagate correctly to the final export artifacts.

Yes, the card data pipeline requires adding tests for new synthesis functions. Adding tests verifies CR-accuracy and ensures that changes to the oracle face building or export paths remain validated.

Yes, you can update card database loading paths within the pipeline. The Skill coordinates changes across loading, synthesis, and export paths, requiring you to run the oracle-gen workflow to verify export consistency.

The best way to maintain CR-accuracy is verifying rules correctness during oracle parsing and synthesis. The pipeline codifies rules for editing these paths and requires regenerating artifacts with the oracle-gen workflow after changes.