No 'driver' in any case: the capitals lines and code terms keep their meaning in other words

check:no-new-driver-references matched 'Driver' only, so lines in capitals
passed unseen (and so did my own grep -w Driver). In my-upg-100-list:
'BATCH-UNION DRIVER' and 'gate drivers' are test handles, so they say so;
'in its driver' is generate.mjs's main routine; the zoning declarations'
'PENDING DRIVER' and 'In DRIVER-DECISIONS-DIGEST' become a pending product
decision and the product-decisions digest. grep -rni driver across both
plugins: 0.

plugin-designs/my-upg-100-list/data/zone-sheet.js

@@ -2,7 +2,7 @@
  * zone-sheet.js — which people groups a map sheet pins, decided ONCE for the Node generator and the
  * browser alike.
  *
- * generate.mjs used to hold this in its driver: attach each leaf zone's selector, then give every
+ * generate.mjs used to hold this in its main routine: attach each leaf zone's selector, then give every
  * people group to the FIRST zone that claims it and pin it there. A browser that draws the same sheet
  * must make exactly the same assignment, or the "same" poster pins a group in a different zone
  * depending on where it was printed. So both import this module; neither keeps its own copy.

plugin-designs/my-upg-100-list/data/zoning-declarations.json

@@ -14,7 +14,7 @@
   },
   "expected_orphans": {
     "_why": "Groups in the list that belong to NO zone. An empty list here means 'every group must be zoned'. A gate cannot tell a deliberate exclusion from a silent drop; only this declaration can.",
-    "_status": "PENDING DRIVER — these 11 are TODAY'S ACTUAL orphans, recorded so the gate is green on arrival and any NEW orphan fails. They are all Japan / China / Mongolia and are plausibly deliberate (asia-china-tibet-autonomous-region is labelled 'Mainland China + Mongolia' and carries only 43 groups), but nobody has said so. In DRIVER-DECISIONS-DIGEST; do NOT change the memberships to make this list shorter.",
+    "_status": "PENDING A PRODUCT DECISION — these 11 are TODAY'S ACTUAL orphans, recorded so the gate is green on arrival and any NEW orphan fails. They are all Japan / China / Mongolia and are plausibly deliberate (asia-china-tibet-autonomous-region is labelled 'Mainland China + Mongolia' and carries only 43 groups), but nobody has said so. In the product-decisions digest; do NOT change the memberships to make this list shorter.",
     "slugs": [
       "ainu-japan",
       "jing",
@@ -31,7 +31,7 @@
   },
   "known_geographic_overlaps": {
     "_why": "Groups that DO sit in two geographic zones, declared so the gate fails on a NEW overlap rather than on these. Not an endorsement — see _status.",
-    "_status": "PENDING DRIVER — uncovered-scatter is country_codes AND,CCK,GUF,USA ('Scattered / Diaspora'), so it overlaps the regional zones it scatters across. Either a scatter zone is a THIRD partition (like a bloc) or these two memberships are wrong. In DRIVER-DECISIONS-DIGEST; do NOT change either membership. ⚠ deaf-cocos-islanders was MISSED by my own hand analysis and found by this gate: I had filtered out every A017 group as 'the design-approved deaf double-count', but its TWO GEOGRAPHIC claims (CCK is in both zones' country lists) are a SEPARATE fact from its bloc membership. Conflating them is exactly what the bloc/geographic split in A2 exists to prevent, and the gate got it right where I did not — which is the best argument for the gate existing.",
+    "_status": "PENDING A PRODUCT DECISION — uncovered-scatter is country_codes AND,CCK,GUF,USA ('Scattered / Diaspora'), so it overlaps the regional zones it scatters across. Either a scatter zone is a THIRD partition (like a bloc) or these two memberships are wrong. In the product-decisions digest; do NOT change either membership. ⚠ deaf-cocos-islanders was MISSED by my own hand analysis and found by this gate: I had filtered out every A017 group as 'the design-approved deaf double-count', but its TWO GEOGRAPHIC claims (CCK is in both zones' country lists) are a SEPARATE fact from its bloc membership. Conflating them is exactly what the bloc/geographic split in A2 exists to prevent, and the gate got it right where I did not — which is the best argument for the gate existing.",
     "slugs": [
       {
         "slug": "deaf-cocos-islanders",

plugin-designs/my-upg-100-list/upg-100-list.vue

@@ -2418,13 +2418,13 @@ onMounted(async () => {
       toggleTerritory(t)
       return { ...t }
     },
-    // ── R1.3 (f″) gate drivers ────────────────────────────────────────────────
+    // ── R1.3 (f″) gate test handles ────────────────────────────────────────────────
     // Toggle a LEGEND ROW by its visible label exactly as a batch-mode legend tap
     // would — resolves the label to its legend node, then routes through
     // toggleZoneSelection (the SAME union path a real row tap uses). Returns the
     // node's descendant zoneKeys (count) so the gate can recompute the expected
     // map-highlight feature count independently.
-    // ⚠ THIS IS THE BATCH-UNION DRIVER, NOT A CLICK SIMULATOR — it calls toggleZoneSelection() directly,
+    // ⚠ THIS IS THE BATCH-UNION TEST HANDLE, NOT A CLICK SIMULATOR — it calls toggleZoneSelection() directly,
     // so OUTSIDE batch mode it toggles a union nobody is displaying and the isolate filter stays
     // undefined. rega measured exactly that (NEEDS-EYES row 45) and asked whether it should isolate for a
     // single select.