Importer Assumes a Standard Sheet

Context and Problem Statement

Early drafts of the Chrono Core Products sheet deviated from the standard sheet conventions (comma-separated multi-values, bracket-wrapped tokens, N/A for absent cells, variant encoded as a rarity suffix, a malformed MK header). We had to decide whether the importer compensates for those quirks or the sheet gets fixed at the source.

Decision Outcome

The sheet is fixed upstream and the importer assumes standard data — pipe-separated multi-values, exact enum tokens, empty cells for absent values, a dedicated variant column, and clean headers. The importer carries no compatibility shims for the legacy format.

What the importer still does beyond plain column mapping:

• set_number ignored — operator bookkeeping, never mapped to any attribute.
• Print-number slug normalization — serialized denominators (1/15) keep a readable - in slugs instead of the stripped / collapsing 1/15 into 115.

Consequences

• ✅ The importer stays minimal; sheet quality problems surface through the base importer’s validation (enum warnings, ensureProductSlugsUnique), not hidden workarounds.
• ⚠️ Import correctness depends on the sheet staying standard — rows sharing the same product group and finish merge silently in the base class (first row wins), like every other sheet game.