@bicharts/shape-core 0.5.40 → 0.5.41

package/dist/types/geoPoint.d.ts

@@ -11,7 +11,7 @@ export type GeoPointResult = {
 export { normalizePlaceName } from "./geoCountryNames";
 /** Which point-map's candidate set a lookup runs against. Rows carry kind flags
  *  (N = North America map, W = World map; a row may carry both), so ONE table serves
- *  every map type with the map deciding its own scope — Joel 2026-08-02: "one row can
+ *  every map type with the map deciding its own scope — 2026-08-02: "one row can
  *  apply to 1 or more map types", and the matching rules are COMMON logic. */
 export type GeoMapKind = "north-america" | "world";
 /** REPLACE the bundled gazetteer with another packed table (same record format). The
@@ -53,7 +53,7 @@ export declare function zipToPrefix3(value: string | null | undefined): string |
 /**
  * THE ZIP READER. One function, because a ZIP arrives in whatever shape the pipeline left it
  * and both matchers — the point cascade here and the choropleth join key in geoDetector —
- * have to read it identically (Joel 2026-08-02: "the matcher to the gazette needs to do
+ * have to read it identically (2026-08-02: "the matcher to the gazette needs to do
  * proper zip matching: it should work for 02108 no matter how the source is interpreted").
  *
  * Everything it survives, and why each one is real:
@@ -85,7 +85,7 @@ export declare function zipPrefixCandidates(value: string | null | undefined): s
  */
 /** The city tier found MORE THAN ONE place the source row could mean, after every
  *  non-blank source attribute was honoured. The row is NOT plotted and the caller
- *  reports it as info — since v2 (Joel 2026-08-02) a guess is never made: "if multiple
+ *  reports it as info — since v2 (2026-08-02) a guess is never made: "if multiple
  *  possible matches are found, that should be a call-out … and it should not be
  *  plotted." Distinct from `null` (nothing matched at all): coarser tiers must NOT
  *  rescue an ambiguity, because the coarser placement would silently pick a side. */
@@ -116,7 +116,7 @@ export type GeoPointColumns = {
      *  Without this a chart can only ever say "22 of 117 positions approximated" — true,
      *  but it cannot say WHICH 22, so it draws every mark as though it were exact. A reader
      *  hovering Inverness got "Inverness, United Kingdom" over LONDON's coordinates, with
-     *  nothing to distinguish it from the London row stacked underneath (Joel 2026-08-04).
+     *  nothing to distinguish it from the London row stacked underneath (2026-08-04).
      *
      *  The counts above are a summary OF this array and remain the right input for a
      *  caption. This is what lets a mark disclose its own precision — style it differently,
@@ -179,7 +179,7 @@ rows: Array<{
 /**
  * The TAGS on a known city ("capital", ...), empty when it carries none or is unknown.
  *
- * The query surface for the per-city tag layer (Joel 2026-08-03: "having tags that can apply
+ * The query surface for the per-city tag layer (2026-08-03: "having tags that can apply
  * at the city level makes sense and can be leveraged in follow-on prompt requests"). `country`
  * narrows to one row when the name is shared ("London" GB vs ON); without it, a name that
  * matches several cities returns the union of their tags, which is honest about what a bare

package/dist/types/matchQuality.d.ts

@@ -3,12 +3,12 @@
  * that column may claim a geographic role.
  *
  * One number for every role — city, state, ZIP, country, and the choropleth region detector
- * (Joel 2026-08-02: "I would prefer one constant, so maybe we make that 95 and apply to all").
+ * (2026-08-02: "I would prefer one constant, so maybe we make that 95 and apply to all").
  * Tune here and they all move together — except CITY, which has its own looser bar below for
  * a reason worth reading.
  *
- * 96 was tried first and SETTLED AT 95 the same day, on evidence rather than taste: Joel's own
- * world_country_metrics carries 42 clean countries and two deliberate junk rows, which is
+ * 96 was tried first and SETTLED AT 95 the same day, on evidence rather than taste: the reference
+ * dataset behind the request carries 42 clean countries and two deliberate junk rows, which is
  * 95.5% — a well-formed reference dataset landing half a point under its own bar. A cliff that
  * a curated 44-row table falls off is in the wrong place. 95 is still far too strict for a
  * column of something else to claim a role by accident (a wrong column scores near zero, not
@@ -33,7 +33,7 @@ export declare const ROLE_MATCH_PCT = 95;
  */
 export declare function isBlankLike(normalized: string): boolean;
 /**
- * CITY is held LOWER, and deliberately so (Joel 2026-08-02: "maybe city is a good one to make
+ * CITY is held LOWER, and deliberately so (2026-08-02: "maybe city is a good one to make
  * lower - 80% even").
  *
  * The other roles are closed vocabularies. There are ~195 countries and ~90 admin1s in scope,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/shape-core",
-  "version": "0.5.40",
+  "version": "0.5.41",
   "description": "Host-agnostic data-shape profiler: ingest a dataset's rows through IValueCollection.addRow and read back the measured shape as an LLMColumnWithValue[] payload — types, cardinality, temporal/ordinal detection, geographic region and point resolution, cross-column signals. MEASUREMENT only: the policy that decides what a measured shape means for chart selection lives server-side.",
   "license": "Apache-2.0",
   "type": "module",