The reference baseline shrinks to the 505 lines still present, so the 181 already reworded cannot return
This commit is contained in:
parent
2506f71e67
commit
c62db6ee4c
1 changed files with 0 additions and 181 deletions
|
|
@ -223,19 +223,6 @@
|
|||
"library/components/map-controls/MapToolbar.vue\u0000shape breaking precisely where the Driver is most likely to look at it.": 1,
|
||||
"library/components/map-controls/ShareButton.vue\u0000/* ★ NO SCROLLBAR — THE MENU SHOWS THE WHOLE SNIPPET (Driver 2026-09-23: \"the share menu that": 1,
|
||||
"library/components/map-controls/ShareButton.vue\u0000LEFT — which is what the Driver asked for, arrived at by measurement rather than by hardcoding a": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// \"these pins are one group\", and that is a Driver taste call, not a legibility defect.": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// 'NUMERALS ARE HELD' (COMMON.md; Driver via shepherd 2026-09-26) covers the whole formatted": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// EVIDENCE FOR THAT RULING, measured here and passed to the Driver's card: a REGIONED tag is what": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// THE REGION COLOURS, CARRIED ONTO THE LANDMASSES (Driver card, 2026-09-24).": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// THE RESTING STATE IS BIGGER THAN THE CLONE'S, and only here. The Driver reported the pins": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// THE SHARED EDGE-SCROLL STRIPS, on by Driver decision (2026-09-24, via shepherd card": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// THEIR MAP CONTROLS, ported verbatim (CountryMap.vue:181-182). The Driver caught that these": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// instead of flying to the region, which is exactly what the Driver reported.": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// the Driver's sanctioned addition and renders under the GLOBE projection, so its subject is a": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// toLocaleString(languageCode). Exact parity is on hold, not abandoned -- when the Driver rules,": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// wastes width. Driver 2026-09-26: \"the only changes are to the map to make it look better, and to": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// ── ★ PRINT: THE LEGEND GOES BESIDE THE MAP, NOT OVER IT (Driver test round 2, #2) ──────────": 1,
|
||||
"library/components/maps/RegionCountryMap.vue\u0000// ★ THE SCROLL STRIPS WERE SWALLOWING THE MAP CONTROLS (Driver, on Mapbox): zoom in, zoom out": 1,
|
||||
"library/components/poster/PosterDialog.vue\u0000* What the Render button does. 'print' (default, Driver rule 2026-09-28: an export-poster button opens": 1,
|
||||
"library/components/poster/PosterWall.vue\u0000// (name / country / population / religion — usePosterPrints.js:150). The PRAYER PACKET the Driver": 1,
|
||||
"library/components/poster/PosterWall.vue\u0000// Driver 2026-09-25, the sticker/olive-oil-bottle brief: this box is a BANNER that DISPLAYS": 1,
|
||||
|
|
@ -367,10 +354,6 @@
|
|||
"plugin-designs/all-people-groups/all-people-groups.vue\u0000* ★ LOAD ORDER (2026-09-25, the Driver: \"not even loading, takes a very long time\"). Pins used to": 1,
|
||||
"plugin-designs/all-people-groups/all-people-groups.vue\u0000// ─── The four categories (the Driver's palette) ──────────────────────────────": 1,
|
||||
"plugin-designs/all-people-groups/all-people-groups.vue\u0000// ★ THE LOCALE-HONOURING FALLBACK, per dx-shepherd's ruling (2026-09-27) and the Driver's goal (d):": 1,
|
||||
"plugin-designs/big-picture/big-picture.vue\u0000// The FOUR real grid axes (Country excluded per Driver).": 1,
|
||||
"plugin-designs/big-picture/big-picture.vue\u0000same number twice, above the fold, which is the redundant-header shape the Driver's": 1,
|
||||
"plugin-designs/big-picture/src/components/BpResearchHeader.vue\u0000* Region / Block / People-Group / Religion. (Country EXCLUDED per Driver.)": 1,
|
||||
"plugin-designs/big-picture/src/components/BpResearchHeader.vue\u0000// the FOUR grid axes (Country excluded per Driver): Region / Block / People-Group / Religion.": 1,
|
||||
"plugin-designs/cities-internet/connectivity-list.vue\u0000// NUMERALS ARE HELD for the Driver (dx-shepherd, 2026-09-26): a locale-following format would switch": 1,
|
||||
"plugin-designs/cities-internet/connectivity-map.vue\u0000// Dark slate with a white ring (Driver 2026-09-28: the red dots looked wrong on the mostly green": 1,
|
||||
"plugin-designs/cities-internet/connectivity-map.vue\u0000// ── People-group dots (Driver: \"red dots on the map to show me where the people groups are\")": 1,
|
||||
|
|
@ -383,14 +366,6 @@
|
|||
"plugin-designs/country-posters/country-posters-mfe.vue\u0000* Driver: \"Country Posters is supposed to have two tabs, structured like the": 1,
|
||||
"plugin-designs/country-posters/country-posters-mfe.vue\u0000* LIST FIRST, MAP SECOND. The Driver's principle, already applied in upg-100-mfe:": 1,
|
||||
"plugin-designs/country-posters/country-posters-mfe.vue\u0000/* ── palette: DX-life material light. NO AUTO-DARK (Driver 2026-09-20): a system set to": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.meta.json\u0000\"_comment\": \"Capability-4 composite that BAKES the research-dashboard + people-groups-grid into ONE self-contained element (both components imported directly + compiled into a single bundle, NO runtime bundle injection — unlike stack-demo which composes via src). Rendered stacked via the shared StackLayout so you scroll through both. This is the 'two elements baked into one' element the Driver asked for.\",": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// Driver couldn't scroll down to the grid. Fix: give this section a definite ONE-SCREEN height": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// NO section title/sub (BUILD-BIGPIC-DROP-REDUNDANT-SECTION-HEADERS). The Driver does not want a": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// THE BUG THIS FIXES (Driver-reported; measured 2026-09-22). Selecting anything in the": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// WITH-GRID). The Driver: \"the people place language, religion sidebar… is not working with": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// title bar), so a StackLayout section title here would be a DUPLICATE — the Driver saw \"Research": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000// ★ COUNTRY WAS THE FIFTH TO EARN ITS MAPPING (Driver-reported 2026-09-22: \"when I click on": 1,
|
||||
"plugin-designs/dashboard-plus-grid/dashboard-plus-grid.vue\u0000<!-- NO explainer line here. An earlier attempt added one as its own <p>, which the Driver": 1,
|
||||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000// (BUG-CANNOT-SCROLL-DOWN-TO-THE-GRID, Driver-reported). Every mounted tab used to get": 1,
|
||||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000// Driver set for the data bundler: handle every plugin generically, or the next author gets": 1,
|
||||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000// RENAMED (Driver): \"Prayer Map\" → \"Prayer Progress\". His words: \"the prayer maps can be renamed": 1,
|
||||
|
|
@ -416,26 +391,6 @@
|
|||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000// ★ THE 404 CLASS THIS REPLACED (measured 2026-09-22, hit by the Driver in his own browser). Every": 1,
|
||||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000empty slot — the grey pane the Driver reported four times. Covering it here means a": 1,
|
||||
"plugin-designs/doxa-maps-spa/doxa-maps-spa.vue\u0000server, so every tab 404'd there — the Driver saw exactly that in his browser console. A path is": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000/* ★ PRINTING THE PAGE COLLAPSED THE MAP AND THREW ITS CHROME UPWARD (Driver, DRV1650-SR-POSTER-EXPORT:": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// Driver's \"the research map isn't connecting with the legend\" on the WAGF Regions tab, found by": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// Driver, 2026-09-24: \"two finger scrolling on the map should allow me to interact with the": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// Prayer progress bar (header of the Prayer tab's legend; Driver 2026-09-16). null on": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// The same in-place frame the Driver's earlier ruling settled on: no pop-up, no blocker, and it": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// and looked right, which is why the Driver reported it as two tabs misbehaving.": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// contract (BUILD-LINKED-FILTERING, Driver 2026-09-25: \"interoperability within themselves\").": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// letterboxes it (Driver, 2026-09-28: the print came out vertical and it should \"probably [be] a": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// search bar above it. Leaving it when the bar is gone is the empty band the Driver called out.": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// the Driver's own rule: an export button opens the print dialog, never hands over a file). This": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ★ ONE CLICK, ONE FILE (BUILD-SIMPLE-RESEARCH-EXPORT-ZERO-CLICK). The Driver: \"there's an export": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ★ THE DIALOG, NOT A DOWNLOAD (the Driver, 2026-09-28: an export-poster button must open the": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ★ THE PACKET PRINTS, AND IT PRINTS THROUGH THE SHARED RENDERER (Driver-lens audit card 2, and": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ★ THE UNDIMMED VALUE IS DATA-DRIVEN TOO, AND THAT IS THE WHOLE POINT (Driver bug: \"the research map": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ★ WHY MAPLIBRE GETS NO SEARCH BAR AT ALL (Driver, 2026-09-23).": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000// ⚠ MOTION SAFETY. The Driver is photosensitive, and a camera that re-animates on every": 1,
|
||||
"plugin-designs/doxa-research-map/research-map.vue\u0000wordmark bottom-left, and two badges there read as a bug (Driver, 2026-09-16). -->": 1,
|
||||
"plugin-designs/doxa-research-map/scripts/check-export-poster-prints.mjs\u0000* check-export-one-click, and it passed while the button did exactly what the Driver has now ruled": 1,
|
||||
"plugin-designs/doxa-research-map/scripts/check-export-poster-prints.mjs\u0000* ★ THE RULE CHANGED, AND THIS GATE ASSERTED THE OLD ONE (the Driver, 2026-09-28: \"an export-poster": 1,
|
||||
"plugin-designs/doxa-research-map/scripts/check-reduced-motion-jumps.mjs\u0000console.log('\\n The Driver is photosensitive. A camera that sweeps on every filter is the defect.')": 1,
|
||||
"plugin-designs/doxa-simple-map/doxa-simple-map.vue\u0000// Prayer progress bar (header of the prayer legend; Driver 2026-09-16). The payload": 1,
|
||||
"plugin-designs/doxa-simple-map/doxa-simple-map.vue\u0000// borders — the \"dark green\" the Driver called our most beautiful map. Without a token the engine": 1,
|
||||
"plugin-designs/doxa-vision-card/doxa-vision-card.vue\u0000* ★ WHY IT WAS REBUILT (2026-09-25). The Driver: \"the data doesn't make sense … super false": 1,
|
||||
|
|
@ -542,142 +497,6 @@
|
|||
"plugin-designs/prayer-walk-planner/prayer-walk-planner.vue\u0000// PHONE: the zone list folds behind a ☰ button (Driver, test round 2 #8) and opens as a drawer over the": 1,
|
||||
"plugin-designs/prayer-walk-planner/prayer-walk-planner.vue\u0000// The Driver: \"the printed map is a ~10px sliver\". Cause, measured 2026-09-25: print used to": 1,
|
||||
"plugin-designs/prayer-walk-planner/prayer-walk-planner.vue\u0000// ★ THE \"VERY TINY MAP\" (Driver; measured 2026-09-25: 747x76 in the Research Gallery at 1280x800,": 1,
|
||||
"plugin-designs/regions-dashboard/index.js\u0000* This bundle ships the Driver's 2-tab Regions element as three flat profiles:": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// (RegionDetail.vue:176) and stretches the same card; the Driver reported it, and dx-shepherd is": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// change to what the Campaign Server shows, so it is the Driver's call and not mine.": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// giveaway (Driver, 2026-09-24). @font-face is DOCUMENT-scoped, so it registers here beside": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// ── ★ PRINT: LET THE DOCUMENT FLOW ONTO PAGES (Driver test round 2, #2) ──────────────────────": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// ★ PRINT (Driver test round 2, #2 — the half the @media print rules could not do). The complaint": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000// ★ auto-FILL WITH A CAPPED TRACK MINIMUM. Driver test round 2: the Population card — the LAST": 1,
|
||||
"plugin-designs/regions-dashboard/region-dashboards.vue\u0000<!-- THE REGION KEY — chooser only, and it is a CONTROL as well as a key: the Driver": 1,
|
||||
"plugin-designs/regions-dashboard/regions-list.vue\u0000// THE COUNTRY-POSTER DROPDOWN (Driver 2026-09-24) — the THIRD sanctioned addition, after the": 1,
|
||||
"plugin-designs/regions-dashboard/regions-list.vue\u0000// giveaway (Driver, 2026-09-24). @font-face is DOCUMENT-scoped, so it registers here beside": 1,
|
||||
"plugin-designs/regions-dashboard/regions-list.vue\u0000// tab for that country — the Driver's \"click view on map button, which will open the country": 1,
|
||||
"plugin-designs/regions-dashboard/regions-list.vue\u0000// the Driver asked for an exact clone of DX-life's OWN design here, so the clone wins.": 1,
|
||||
"plugin-designs/regions-dashboard/regions-list.vue\u0000// ★ THIS PAGE ASKS FOR TWO FIELDS, NOT EIGHT. The Driver reported the list page being slow and": 1,
|
||||
"plugin-designs/regions-dashboard/regions-mfe.meta.json\u0000\"note\": \"The Driver's 2-tab Regions element. Composite MFE on the pane-wrapper layout, imitating my-upg-100-list/upg-100-mfe: a SELECT VIEW switcher (library/components/ViewSelect.vue) over Regions List at [0,0] and Region Dashboards at [1,0]. Clicking a region or country on tab 1 forwards the selection on 'doxa-regions-dashboard:select' and swaps to tab 2. pinHint:false: the cloned pages carry no coach-mark, and the composite must declare it because a pane's config comes from here, not from the child's own meta.\",": 1,
|
||||
"plugin-designs/regions-dashboard/regions-mfe.vue\u0000* and the Driver named it explicitly as the thing to copy. Same shape, tab for tab:": 1,
|
||||
"plugin-designs/regions-dashboard/scripts/check-regions-uses-library.mjs\u0000// ── REGLIB batch 2: the Driver's \"banners/cards that tell you the prayer progress\" ─────────────": 1,
|
||||
"plugin-designs/regions-dashboard/src/UupgsList.vue\u0000// allows, and the Driver ruled it must not ship in a public giveaway (2026-09-24).": 1,
|
||||
"plugin-designs/regions-dashboard/src/UupgsList.vue\u0000// us DIFFER. Flagged for the Driver: the upstream fix is one word, in their file.": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// \"Big Picture Research Dashboard\" (Driver 2026-09-20). The share button embeds THIS whole": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// 'greyscale' is the Driver's requested swappable alternative (\"grey scale as a backdrop": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// (one of the Driver's four axes) renders as a near-empty stub and looks broken.": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// Driver: \"if you had a team of people trying to fill the globe with the gospel… they need to be": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// NOT a ninth dropdown, and the reason is the Driver's list, NOT layout. Measured at both 1440": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// a working baked token (the Driver's explicit ruling accepted it as public). MapLibre support": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// earlier note above about \"the Driver named eight ... engagement was the one missing\" describes a": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// for this one, where 150 is a deliberate, Driver-chosen number.": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// is what moved. Driver: \"that filter of 150 ... should be a variable. It shouldn't be a": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// other's selection. Driver, from behaviour: \"there are duplicate affinity blocks, one": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// second row — so the layout would tolerate it. The list stays at the eight the Driver named;": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// trees read as the stack the Driver asked for rather than as five peers.": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// ★ CORRECTED 2026-09-23 — this note used to say \"GSEC is the underlying field the Driver named": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// ★ EIGHT dropdowns. The Driver named them: \"people, region, block, country, language, religion,": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// ★ HIGH-LEVEL RELIGIONS ONLY (Driver 2026-09-23: \"it should not mention Ethnoreligion and": 1,
|
||||
"plugin-designs/research-dashboard/dashboard.config.js\u0000// ★ SWITCHED TO GREYSCALE 2026-09-23 on the Driver's ruling: \"instead of the red, we need to": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000\"grey spot between the height of the map\" the Driver reported twice.": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000/* ★ COLLAPSE GIVES ITS SPACE TO THE MAP (Driver 2026-09-23: \"collapsing the table is supposed to": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000/* ★ SEVEN DATA ROWS BY DEFAULT (Driver 2026-09-23, and he did the arithmetic himself):": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000/* ★ SYMMETRIC SIDEBARS (Driver 2026-09-23: \"the charts sidebar can be wider so it is the": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000/* ★ THE ELEMENT MUST SIZE TO ITS CONTENT IN PAGE-SCROLL (Driver 2026-09-23: \"massive grey gap": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000// was unreachable by the gesture the Driver actually makes.": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u00004 of 5 trees open by default (the Driver's own correction, see DashboardFacetRail's": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u000064px WIDER than the tree, which is exactly what the Driver saw (\"it looks like the": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000band were both already driven to a Driver-set floor in earlier cards; see their own notes).": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000in a693865 and the Driver caught immediately: \"the height of the table is smaller now, but that": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the Driver three separate times. Pinning the ROW to the same var the ELEMENT uses makes them": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the Driver's \"visible on one desktop page\" invariant does not allow. calc() derives the": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the Driver's 2026-09-23 ruling), and that is DELIBERATE, not drift: a basemap is imagery the": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the control the Driver actually asked for — \"resize the height of the page\" — which a previous": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the right, which is the \"justified left\" the Driver is describing.": 1,
|
||||
"plugin-designs/research-dashboard/research-dashboard.vue\u0000the surplus painted as the grey band the Driver reported between/under map and table, and": 1,
|
||||
"plugin-designs/research-dashboard/scripts/check-dashboard-filter-a11y.mjs\u0000// author to mount something the Driver asked to have removed.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000* Charts is selected by default, which is the Driver's wording: \"Charts will be a SELECTED TAB": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000* placeholder. Its content is not a separate dataset panel — the Driver described it as the SAME": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000* title attribute tells the Driver exactly what it is waiting on, every time he looks at the rail —": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000/* The donut legend is the WORST offender the Driver reported: a short, always-scrolling list": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000/* ★ THE CONVENTIONAL LEGEND ROW, on the Driver's final ruling (2026-09-23): \"I am not": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000/* ★ THE COUNT COLUMN IS UNIFORM, RIGHT-JUSTIFIED AND IMMOVABLE (Driver 2026-09-23: \"set the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000/* ★ THE COUNT IS A FROZEN COLUMN (Driver 2026-09-23): \"the number column was supposed to be": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000// COUNTRY -> REGION hue (the Driver's \"countries should match the colour of their regions\").": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000History: (1) capped at 108px to match the donut, which forced ELLIPSIS; (2) the Driver rejected": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000It is reversed on the Driver's explicit ruling: measured before this change, 4 of 16 legend": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000The Driver has now ruled READABILITY OVER COMPACTNESS (2026-09-22): \"on the religion and": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000tab ENCODES is not, because it waits on three open Driver decisions (the official lostness": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000that cap is precisely what forced the unreadable ellipsis the Driver rejected. */": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000while 4 were actually truncated, including the two the Driver had just complained about.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardChartsRail.vue\u0000★ THE RAIL IS A TAB STRIP, NOT A HEADING (Driver: \"I asked a long time ago that the chart": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000* by default because the Driver is reclaiming vertical space. A deliberately small table is only": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000/* ★ MEASURED AT 1280 (the Driver's flood, second cause): hiding the hint was not enough -- the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000/* ★ NO ELLIPSIS ON THE HEADER (Driver: \"instead of ABBREVIATING the headers, we can have the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000// Driver asked to stop abbreviating: a column must never be narrower than its own full title.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000// the Driver objected to was happening.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000// ★ NATIVE FULLSCREEN, NOT A FIXED OVERLAY (Driver 2026-09-23: \"there is no way to exit full": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000<!-- ★ NO CLEAR BUTTON IN THIS BAR (Driver 2026-09-23, on the selection flood: \"it does not": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000Out of flow means it adds ZERO height by construction — the Driver's hard constraint.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000controls the Driver asked to keep docked under the map when the grid is hidden. -->": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000header above the grid, the Driver asked for it to ride the EXISTING bar instead, and it was": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000one row selected the bar wrapped to 43px and pushed a control out of it -- the Driver's": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardDataTable.vue\u0000★ NO EXPLANATORY HINT HERE (Driver, 2026-09-22: \"there does not need to be this text in the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000/* Plain BLACK behind the sphere (Driver: \"if not, then just do black background, not grey\").": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000/* ★ THE GALAXY IS THE CONTAINER, NOT THE TILES (Driver 2026-09-23, correcting the first attempt:": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// \"Reverting to orange - the Driver ruled explicitly against it.\" ★ NO LONGER TRUE. That": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// '#fff' at full opacity, because the Driver asked for WHITE rings and 0.95 alpha over a": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// (Driver 2026-09-22: \"the pins look like eyes, they look kind of creepy\")": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// Blue dots + white rings are the Driver's own settled ruling (\"I like the blue dots. Do not": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// Driver 2026-09-22: \"keep every Mapbox component working so we don't break Mapbox": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// Driver decision with a contrast analysis attached (see the long note on the layer's paint block:": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// Driver is describing. The densest data cell (75E/15N) was shoved to x=939, onto the right": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// Driver's own word for it (\"those are the heartbeat zones\", \"God's heart beats loudest for the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// NON-UNIFORM lightness steps, so the TOP of the ramp — where the Driver's complaint actually": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// change: space-color is pure black on the Driver's instruction (\"not grey\"). star-intensity": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// deliberate and bought the hue the Driver asked for while still clearing the 7:1 floor that was": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// family and reads as brown. Rejected on spec, not on score — the Driver asked for orange.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// giving the Driver back a navy pin or giving up the label red.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// here — this pin is ONE fixed colour at FULL opacity, never tinted per bin. The Driver's": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// indication why. But dashboard.config.js pins provider:'mapbox' DELIBERATELY — the Driver's own": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// light symbol wants a DARK ground. The constraint did not get violated, it INVERTED. The Driver's": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// merged into the \"heat map\" look the Driver reported. Paling the ramp (above) fixes the": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ruling was given while the ramp was PALE and the pin navy; the Driver has since asked for": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// separation is real and larger; whether it now READS as \"clearly distinct\" is the Driver's call.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// that does not respond; the remaining budget went to the Driver's actual spec, the label red.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// was on the map — which is a strong candidate for the Driver's report that \"60-149 red is the same": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// whole derivation: the Driver named a brand family, and the family has coordinates.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// why the Driver tied it to the globe/flat setting: flat shows the same bad center, but a": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// zoomed-out view where the Driver saw the heat map. The footprint at z1 drops 24%, which": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ── Table selection -> camera (the Driver's ask: \"select in the table, the map zooms there\") ──": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ╔═ BUG-CAMERA-FLIES-TO-NORTH-POLE-ON-FLAT-FACETS (Driver, 2026-09-22) ════════════════════╗": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ★ BIN 1 DARKENED #e8e8e8 -> #c9c9c9 (Driver 2026-09-23: \"bangladesh is not showing up as a": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ★ SUPERSEDED BY --rd-map-h (BUG-MAP-ZOOM-BROKEN-BY-THE-SCROLL-FIX, Driver-reported 2026-09-23).": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ★ THE GALAXY, THE WAY MAPBOX DOES IT (Driver: \"find out how Mapbox does the galaxy stars and": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ★ THE TWO ENGINES DISAGREE ON THIS ONE CALL, AND THE CATCH HID IT (Driver 2026-09-23: \"the map": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000// ★ ZOOMED OUT BY DEFAULT, WITH REAL ZOOM-OUT RANGE (Driver 2026-09-23: \"I don't want the map": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardMapPanel.vue\u0000of the band, so the Driver's cursor lands on it and scrolling feels completely dead.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardResearchFilters.vue\u0000/* ★ 5px -> 3px. The band's own padding is the FOURTH owner of what the Driver sees as one": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardResearchFilters.vue\u0000// (0 < n < 144) / full (n >= 144). Three levels => a DROPDOWN, which is also where the Driver": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardResearchFilters.vue\u0000// ★ THE TYPED SEARCH IS A FILTER AND MUST LOOK LIKE ONE (Driver 2026-09-23: \"I searched Bhutan": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardResearchFilters.vue\u0000filters\" the Driver named (card BUILD-SELECTED-ROW-MUCH-THINNER-AND-CENTRED). The band's own": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000* came back green while the Driver was plainly still looking at his selection in the top bar. A": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000* not a readout of it, and the Driver's sentence names it as this header's defining occupant.": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000/* SHARE in this bar (Driver 2026-09-28: \"too large\"). ShareButton is the map toolbar's 40px round button": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000/* ★ FULL PILL, not a bigger number picked by eye (Driver: \"I want the search bar in the top": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000<!-- SHARE the WHOLE dashboard (Driver 2026-09-20): \"if we could actually embed this on a": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000at 1024x768) — the Driver has said NEVER add a second header row. */": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000decision the Driver already made in the other direction, so it is asked rather than assumed. */": 1,
|
||||
"plugin-designs/research-dashboard/src/components/dashboards/DashboardTopBar.vue\u0000people-groups-grid and big-picture too, which the Driver did not ask for. Verify what actually": 1,
|
||||
"plugin-designs/research-dashboard/src/composables/useDashboardAggregations.js\u0000* COUNTRY -> REGION HUE. The Driver's ask: \"countries should match the colour of their regions.\"": 1,
|
||||
"plugin-designs/research-dashboard/src/composables/useTreeLegendColors.js\u0000* Driver's ruling: the legend's colours must come from the cap-3 research map's semantic tree, so": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.meta.json\u0000\"_comment\": \"Capability-4 composite: the monolithic doxa-research-map (cap-3) stacked above the people-groups-grid (cap-2), scrolled as one element. THE MOBILE SIBLING of dashboard-plus-grid — the Driver's 2026-09-22 ruling was two separate cap-4 plugins rather than one element that swaps its top half by aspect ratio ('that would be really complex'); the SPA picks which one to show. Composes by TAG + BUNDLE URL (the stack-demo element/src contract) rather than baking the children in, because importing the research map's .vue directly would bypass doxa-research-map/index.js and silently drop its bundle-private colour strategies, its profileModules registry, its Pinia/i18n pair and the RTL plugin. The grid's own search + filters are ON here (unlike the desktop sibling, where the dashboard header owns them).\",": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000* dashboard on desktop, research map on mobile. The Driver reversed that mid-message, verbatim:": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000* searched or filtered at all. Driver, verbatim: the grid's search bar + filters must be toggled": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000* ── WHY THIS EXISTS AS A SEPARATE PLUGIN (Driver 2026-09-22) ─────────────────────────────────": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000// here would render the name twice — the duplicate-header bug the Driver rejected on the desktop": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000// ─── ONE FILTER STATE, TWO HALVES (BUILD-LINKED-FILTERING, Driver 2026-09-25) ───────────────": 1,
|
||||
"plugin-designs/research-map-plus-grid/research-map-plus-grid.vue\u0000// ★ NO FLY/CLUSTER TOOLBAR IN THE COMPOSITE (Driver, 2026-09-23).": 1,
|
||||
"plugin-designs/research-map-plus-grid/scripts/check-hover-channel.mjs\u0000* bug wearing a new hat, on a Driver who is photosensitive.": 1,
|
||||
"plugin-designs/research-map-plus-grid/scripts/check-ui-strings-have-keys.mjs\u0000* NO KEY wording must be written and translated — a decision, sometimes the Driver's.": 1,
|
||||
"plugin-designs/research-map-plus-grid/scripts/check-ui-strings-have-keys.mjs\u0000console.log(' Driver\\'s call. A string that HAS a key needs one edit: the work is already done.')": 1,
|
||||
"plugin-designs/upg-neighbor/src/campaigns.vue\u0000// reach, the letter's audience (Driver, test round 2: \"on the Campaign side you can't click green dots\").": 1,
|
||||
"plugin-designs/upg-neighbor/src/letter.js\u0000* letter.js — the LETTER to a reached group's believers (Driver, test round 2: UPG Neighbor is a letter": 1,
|
||||
"plugin-designs/upg-neighbor/src/mobilize.vue\u0000// BOTH DIRECTIONS (Driver, 2026-09-28): a red dot shows the reached groups to mobilize for it; a green dot": 1,
|
||||
|
|
|
|||
Loading…
Reference in a new issue