Reconcile pending scan submissions after catalog sync #51
No reviewers
Labels
No labels
agent-context-drift
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rstillwell/deckhearth#51
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/reconcile-submissions-after-catalog-sync"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
lib/card-import/reconcile-submissions.jsto match pendingcard_submissionsagainst catalog rows after each set import (set code/name + card name + collector number, with015/208↔15/208normalization).status = 'approved'andpromoted_card_idto the existing catalog row (no duplicatecardsINSERT).runCatalogSyncafter every successfully imported set; surface counts in the admin catalog sync panel.Behavior
pendingsubmissions whoseocr_payloadreferences the imported set are considered.reviewed_byremains null on auto-reconciled rows (manual admin approvals still set it).Test plan
npm run test:run— 45/45 green (5 new reconciliation unit tests)/admin/card-submissionsandpromoted_card_idis setMade with Cursor
The latest updates on your projects. Learn more about Vercel for GitHub.
Pipeline Health
Build + CI gates
Build runs on Vercel; this CI runs lint and schema-map drift only (no duplicate build).
Role reports
See individual comments above for details. This rollup updates automatically.
Visual Diff
Screenshots and diffs uploaded as artifacts: view run
If intentional changes: update snapshots locally with
npx playwright test --project=visual --update-snapshotsand commit.