Implement Lorcana Card Batch
Use lorcana-cards as the behavior owner and lorcana-find-card to resolve
each card. There is no maintained source-file queue; never delete source rows
as a completion signal.
Workflow
- Build a bounded queue from the user's list or an explicit
missingImplementation: truesearch. - Record each card's definition and test paths before assigning work.
- Parallelize only cards with disjoint definition and test files. Keep shared engine, types, exports, and generator files under one owner.
- Require one focused behavior test and one structured result per card:
implemented,already-done,skipped, orblocked. - If two cards expose the same engine gap, stop the batch and fix that shared primitive once before continuing.
- Review the combined diff, run affected card tests, then run the package check once.
Do not remove source records, stage broad paths, or let concurrent workers edit the same shared file.