fix(client): accept lowercase set codes in MTGA deck lines

[jeffrey701]

Problem

parseDeckEntryLine matches MTGA-style printing lines (<count> <name> (<set>) <collector#>) with:

/^(\d+)x?\s+(.+?)\s+\(([A-Z0-9]*)\)\s+(\S+)(?:\s+.*)?$/

The set-code group is [A-Z0-9]* — uppercase only. MTGA_LINE_PATTERN (used for format detection) has the same restriction. A decklist line whose set code is lowercase (Scryfall-style — e.g. 2xm, mh2, m21, fdn, which several exporters emit) fails the MTGA match, falls through to the simple (\d+)x?\s+(.+) matcher, and the set code + collector number get swallowed into the card name:

"1 Lightning Bolt (2xm) 123"  ->  { count: 1, name: "Lightning Bolt (2xm) 123" }   // no sourcePrinting; name won't resolve

Fix

Widen the set-code class to [A-Za-z0-9]* in both the parse regex and MTGA_LINE_PATTERN. setCode.toLowerCase() already normalizes case downstream, so a lowercase code yields exactly the same sourcePrinting an uppercase one would. Card names never contain a parenthesized (...) <token> run, so widening the class can't misclassify a real name line.

Tests

Adds two cases to the existing deckParser suite: a lowercase set code ((2xm) 123) now parses to { name: "Lightning Bolt", sourcePrinting: { setCode: "2xm", collectorNumber: "123" } } (fails before — the name is garbled and there's no printing), and lowercase vs uppercase set codes produce identical results. The full existing 73-test suite still passes.

Self-contained: only deckParser.ts + its test; no engine/Rust/protocol changes.

Model: claude-opus-4-8

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!