@bicharts/chart-host 0.5.70 → 0.5.72

package/dist/index.mjs

@@ -750,10 +750,11 @@ function computeQualifyFilterView(groups, term) {
     if (grp.heading !== null) (any ? showHeadings : hideHeadings).push(grp.heading);
   }
   const filtering = fit.tier !== "all";
-  const openRefusals = filtering && fit.rows.length === 0 && ref.rows.length > 0;
+  const nameOnlyBelow = fit.tier === "desc" && (ref.tier === "name" || ref.tier === "namePart");
+  const openRefusals = filtering && ref.rows.length > 0 && (fit.rows.length === 0 || nameOnlyBelow);
   let note = "none";
   if (filtering) {
-    if (fit.tier === "desc") note = "descFallback";
+    if (fit.tier === "desc") note = nameOnlyBelow ? "descAndRefusalName" : "descFallback";
     else if (fit.tier === "none") note = openRefusals ? "onlyRefusals" : "noMatch";
   }
   return {

package/dist/types/qualifyFilter.d.ts

@@ -216,15 +216,20 @@ export interface QualifyFilterGroup<E> {
  *
  *  "none"         - a name tier answered, or nothing is being filtered. Say nothing: the reader's
  *                   own word was found where they expected it and needs no explanation.
- *  "descFallback" - no name matched; these matched on description. MUST be said - a silent
- *                   fall-through is indistinguishable from bad matching.
+ *  "descFallback" - no name matched ANYWHERE; these matched on description. MUST be said - a
+ *                   silent fall-through is indistinguishable from bad matching.
  *  "onlyRefusals" - nothing that FITS matches, but something in the refusal block does. Say where
  *                   it went; that block is now open.
+ *  "descAndRefusalName" - both at once, and the state that made this a five-way rather than a
+ *                   four-way decision (2026-09-04). The fitting list answered on DESCRIPTION and
+ *                   the refusal block answered on a NAME, so "no name matches" is a lie told over
+ *                   the top of a visible name match, and the reader's own word needs BOTH halves
+ *                   said: why the rows above look unrelated, and where the row they typed went.
  *  "noMatch"      - nothing anywhere. NEVER phrase this like "nothing fits your data": one is a
  *                   statement about a typed string and is fixed with backspace, the other is a
  *                   statement about the data and is not.
  */
-export type QualifyFilterNoteKind = "none" | "descFallback" | "onlyRefusals" | "noMatch";
+export type QualifyFilterNoteKind = "none" | "descFallback" | "onlyRefusals" | "descAndRefusalName" | "noMatch";
 export interface QualifyFilterView<E> {
     /** Rows to show, and rows to hide. Two lists rather than one predicate so a host can write
      *  them in one pass without asking a Set per element. */
@@ -243,11 +248,17 @@ export interface QualifyFilterView<E> {
     /**
      * Does the refusal block need to be OPEN for this term?
      *
-     * True only when the term matches nothing that fits and something that does not. "Why isn't
-     * my chart here" is the only question that section is open to ask, and the reader has just
+     * True when the block holds a match the fitting list cannot show the reader. "Why isn't my
+     * chart here" is the only question that section is open to ask, and the reader has just
      * asked it by name - the server's own sentence about why it cannot be drawn is already
      * rendered, one collapsed checkbox away.
      *
+     * TWO WAYS TO EARN IT, and the second was missing until 2026-09-04: nothing that fits
+     * matched at all, OR the only NAME match is down there while the fitting list answered on
+     * description. A description match above is not a substitute for the row the reader typed -
+     * it is a weaker tier, and leaving the block shut hides the actual answer behind a checkbox
+     * the reader has no reason to tick.
+     *
      * THE HOST MUST TREAT THIS AS AN OVERRIDE, NOT A SETTING: remember what the reader's own
      * checkbox said before the first override, and put it back the moment this goes false. An
      * auto-expansion that sticks leaves the reader with a section they never opened.

package/dist/types/qualifyLaunch.d.ts

@@ -131,13 +131,23 @@ export declare function shouldOpenChooserOnGenerate(i: ChooserGateInput): boolea
  * a card that CLIPS, so past a certain smallness its buttons are simply not on screen and the
  * reader is trapped. A panel that flows inside a scrolling pane, with a wrapping button row,
  * cannot reach that state: swept across 63 pane sizes down to 200x120, every one stayed usable
- * - the footer wrapped from one line to three (38px to 86px) and stayed inside the panel, and
- * the list kept four or more rows because it carries its own max-height and scrolls.
- *
- * So a size clause here would not protect anybody; it would only switch the feature off for a
- * default task pane, which is narrower than the modal's floor. Two hosts, two layouts, two
- * honest answers - written next to each other so the difference reads as a decision rather than
- * as one of them having forgotten.
+ * - the footer wrapped from one line to three (38px to 86px) and stayed inside the panel.
+ *
+ * So a size clause here would not protect anybody. Two hosts, two layouts, two honest answers -
+ * written next to each other so the difference reads as a decision rather than as one of them
+ * having forgotten.
+ *
+ * TWO CLAIMS THIS COMMENT USED TO MAKE HAVE BEEN WITHDRAWN (2026-09-04), because the modal's
+ * re-measure discredits the sweep they came from rather than this function:
+ *
+ *   * "a default task pane is narrower than the modal's floor" - it no longer is. The floor moved
+ *     to 320x220 and an ordinary task pane clears it, so the two gates now agree on the pane that
+ *     used to be the whole argument. The asymmetry survives only below the card's drawable
+ *     minimum, which is the only place it ever described something real.
+ *   * "the list kept four or more rows" - measured the same way the modal's rows were, which is
+ *     to say without the DESCRIPTION every row carries. Whatever that number is, it is not four,
+ *     and no claim is made here in its place. It was never the reason for having no size clause:
+ *     the panel scrolls and the footer wraps, and THAT is the reason.
  */
 export declare function shouldOpenInlineChooserOnGenerate(i: {
     enabled: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bicharts/chart-host",
-  "version": "0.5.70",
+  "version": "0.5.72",
   "description": "Run a BIC-generated D3 chart in any web host: compiles the generated render() function, applies the shared option defaults, resolves mark clicks (through tooltip overlays), owns the selection affordance, and translates row indices between cross-filtered charts. The same contract the BIC Power BI visual implements, minus Power BI. React bindings at @bicharts/chart-host/react.",
   "license": "Apache-2.0",
   "type": "module",