The charger's own card list gets a door, and says where it differs

0104 was already implemented and already in the action catalogue; nothing
routed to it, so the only way to see the device's list was as a side
effect of writing a card. It has an endpoint now, and the panel a button.

The two lists are compared where they meet: a card the charger holds and
the account has forgotten still opens it, and a card only the account
holds will not, and neither shows anywhere else. The comparison is drawn
only when they disagree, and the device's reading is dropped on a refresh
rather than measured against an account list from a later moment.

The new test asks all four card routes without a token: a capability the
plugin implements and the catalogue advertises is still unusable if
nothing routes to it, and no other test here would notice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Web App/web/src/i18n/da.json

@@ -80,6 +80,13 @@
       "namePlaceholder": "Navn (valgfrit)",
       "notAdded": "Tjenesten tog imod anmodningen, men kortet er ikke på laderen. Kontrollér nummeret, og prøv igen.",
       "notRemoved": "Tjenesten tog imod anmodningen, men kortet er stadig på laderen.",
+      "readCharger": "Læs laderens egen liste",
+      "chargerTitle": "På selve laderen",
+      "chargerNone": "Laderen har ingen kort.",
+      "chargerHint": "Spurgt laderen, ikke kontoen. Den svarer kun med numre — et korts navn hører til på kontoen.",
+      "driftTitle": "De to lister er ikke enige",
+      "onlyOnCharger": "Åbner laderen, men findes ikke på kontoen: {cards}",
+      "onlyOnAccount": "På kontoen, men ikke på laderen, så det åbner den ikke: {cards}",
       "inferred": "Anker dokumenterer hverken tilføjelse eller fjernelse. DriverVault udleder anmodningen af de felter, kortlisten svarer med, og læser derefter listen igen — det, du ser ovenfor, er det, kontoen har."
     },
     "stations": {