From 7b494facf5119c10ae0cb5f6c8b73df0f459abc2 Mon Sep 17 00:00:00 2001
From: Doxa Maps <maps@doxa.example>
Date: Tue, 29 Sep 2026 05:18:57 +0000
Subject: [PATCH] The browser-side generator keeps the reason and drops the
 speaker

library/packet/poster-render.js and posterSheets.js arrive in this landing
carrying the generator's comments as they stood before the sweep: two lines
named the Driver and one said "he changed the SHAPE". They are reworded as
the sweep reworded them in generate.mjs, and two pronouns the sweep left
behind (SearchFilterHeader, check-filter-width-stable) now say what was
asked instead of who asked. The baseline drops the two generate.mjs lines
that moved out.
---
 internal/check-filter-width-stable.mjs            | 2 +-
 internal/fixtures/driver-references-baseline.json | 4 +---
 library/components/search/SearchFilterHeader.vue  | 2 +-
 library/packet/poster-render.js                   | 8 ++++----
 library/packet/posterSheets.js                    | 2 +-
 5 files changed, 8 insertions(+), 10 deletions(-)

diff --git a/internal/check-filter-width-stable.mjs b/internal/check-filter-width-stable.mjs
index b530057f5..c7ad07ad4 100644
--- a/internal/check-filter-width-stable.mjs
+++ b/internal/check-filter-width-stable.mjs
@@ -9,7 +9,7 @@
  *
  * ★ WHY IT IS NOT COSMETIC: the selections row with Clear All sits
  * UNDERNEATH the filters. If a filter grows on selection, the row below re-flows and the whole group
- * stops being the aligned block he asked for. The stable width is what makes the centred stack hold
+ * stops being the aligned block that was asked for. The stable width is what makes the centred stack hold
  * still — so this is a layout invariant, not a preference about widths.
  *
  * The ellipsis rules were already present and doing nothing: `.filter-dropdown__label` lacked
diff --git a/internal/fixtures/driver-references-baseline.json b/internal/fixtures/driver-references-baseline.json
index 64df9b765..c1df11523 100644
--- a/internal/fixtures/driver-references-baseline.json
+++ b/internal/fixtures/driver-references-baseline.json
@@ -83,9 +83,7 @@
   "plugin-designs/gospel-resources/scripts/build-people-group-pins.mjs\u0000// WHAT IT IS WORTH ANYWAY: the Driver asked for the people who do the": 1,
   "plugin-designs/gospel-resources/scripts/fetch-doxa-people-groups.mjs\u0000* This map was built on the full 12,379-pin people-groups dataset, and the Driver's reading": 1,
   "plugin-designs/my-upg-100-list/poster-wall.vue\u0000* The last two are a Driver ruling, not a preference (2026-09-23): \"three print buttons, each": 1,
-  "plugin-designs/my-upg-100-list/poster-wall.vue\u0000// (generate.mjs:93) and that is an open question for the Driver about what a print artifact is": 1,
   "plugin-designs/my-upg-100-list/poster-wall.vue\u0000// Product call taken by dx-shepherd (UPGHK, 2026-09-27) under the Driver's standing goal that the": 1,
-  "plugin-designs/my-upg-100-list/poster-wall.vue\u0000// while every word of the interface AROUND them was translated. Found in gospel's Driver-lens": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// Carded for the Driver: 27 geographic / 29 counting deaf, and whether \"Central Asia + Pakistan\"": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// Driver called \"the only way that map would be usable\".": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// Driver kept reporting. One host cannot be fixed by breaking the other, so the offset is": 1,
@@ -104,7 +102,7 @@
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// ★ PRINT STRAIGHT FROM THE MAP — the Driver's \"that's the only way that map would be usable\".": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// ★ REVERTED TOWARD THE SIBLINGS (Driver 2026-09-23: \"the dots are way too big, I never": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// ★ THE ONE SEAM THE `list` PROP WILL FEED. Driver 2026-09-26 via the shepherd: UPG-100 is the mass": 1,
-  "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// ★ primary_language + imb_gsec FEED THE GENERATED PROFILE DESCRIPTION (Driver brief A1.5 col 2,": 2,
+  "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000// ★ primary_language + imb_gsec FEED THE GENERATED PROFILE DESCRIPTION (Driver brief A1.5 col 2,": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000<!-- ★ NO MAP-LEVEL SHARE BUTTON HERE (Driver 2026-09-23, reported twice): \"there's a share": 1,
   "plugin-designs/my-upg-100-list/upg-100-list.vue\u0000<!-- ★ THE SELECTION MAKES SOMETHING. Driver: the batch tool is \"super buggy\", and letting": 1,
   "plugin-designs/my-upg-100-list/upg-100-mfe.vue\u0000/* NO AUTO-DARK. The DX design pattern is material LIGHT (Driver 2026-09-20): a system set to dark": 1,
diff --git a/library/components/search/SearchFilterHeader.vue b/library/components/search/SearchFilterHeader.vue
index f9f33c8d1..0e453d533 100644
--- a/library/components/search/SearchFilterHeader.vue
+++ b/library/components/search/SearchFilterHeader.vue
@@ -332,7 +332,7 @@ function onClearAll() { emit('clear-all') }
    MEASURED with the eighth dropdown (engagement/Status) added: the dropdowns are a fixed 168px on a
    200px pitch, so eight need ~1428px. At a 1440 viewport that just fits (maxRight 1428); at 1280 it
    did not, and sfh__filters-row reported scrollWidth 1414 against clientWidth 1252 — a scrollbar,
-   exactly what he asked not to see.
+   exactly what was asked not to be shown.
    Wrapping is the right lever rather than shrinking the dropdowns: their fixed 168px width is itself
    a product decision (filters not so wide), and a flexible width was what made them jump as a
    selection changed. So the row now flows onto a second line when it must.
diff --git a/library/packet/poster-render.js b/library/packet/poster-render.js
index 0ce802240..0da5d3fa0 100644
--- a/library/packet/poster-render.js
+++ b/library/packet/poster-render.js
@@ -3,8 +3,8 @@
  *
  * ★ WHY IT MOVED HERE. The zone and country map sheets (the posters, and the map-only sheet on a
  * packet's page 1) were drawn only by library/scripts/posters/generate.mjs, a Node script: the browser
- * could print a sheet only if one had been generated ahead of time and STORED. The Driver's rule for
- * the print standard is the opposite — every export is generated at the moment it is asked for, and
+ * could print a sheet only if one had been generated ahead of time and STORED. The print
+ * standard's rule is the opposite — every export is generated at the moment it is asked for, and
  * only true previews are stored. This file is that generator with its Node half taken off: the drawing
  * code is moved here byte-for-byte, and everything it used to read from the machine is now PASSED IN.
  *
@@ -2147,10 +2147,10 @@ async function renderPoster(zone, pins, zoneFC) {
   // to run the SAME number of lines in each column — that is what makes three
   // columns read as one band instead of three unequal blocks, and it costs a line
   // of height, which goes back to the map.
-  // ★ FROM series.json, NOT FROM HERE. These three blocks were the Driver's second complaint: they
+  // ★ FROM series.json, NOT FROM HERE. These three blocks were the second reported problem: they
   // tell the reader to divide the set among THIRTY disciples, which is coherent for ~30 UPG-100
   // zones and incoherent for ~170 country posters. The country wording is not a find-and-replace of
-  // "thirty" with "a hundred and seventy" — he changed the SHAPE, from "split the set" to "ask
+  // "thirty" with "a hundred and seventy" — the SHAPE changed, from "split the set" to "ask
   // which one, then give them that poster". Both sets live in series.json.
   // ENGLISH ONLY, on purpose: this file does no localization at all (no PACKET_LANG, no
   // packet-strings, and its non-ASCII characters are entirely typographic — no translated string
diff --git a/library/packet/posterSheets.js b/library/packet/posterSheets.js
index c0c9032ed..3a0e6f3cb 100644
--- a/library/packet/posterSheets.js
+++ b/library/packet/posterSheets.js
@@ -1,7 +1,7 @@
 /**
  * posterSheets.js — generate a map sheet IN THE BROWSER, at the moment it is asked for.
  *
- * The print standard's rule (Driver 2026-09-29): exports are generated, not stored; only true previews
+ * The print standard's rule (2026-09-29): exports are generated, not stored; only true previews
  * are stored. The map sheet — a poster, or the map-only sheet on a packet's page 1 — used to exist only
  * if the Node generator had written it ahead of time. poster-render.js is that generator as a pure
  * factory; this module is its browser feed: it loads the two tables every sheet shares (the series