@@ -44,13 +44,20 @@ describe('resolveFieldScale', () => {
     expect(resolveFieldScale({ type: 'percent', scale: 0 })).toBe(0);
   });
 
-  it('declares NO width for number and currency — the census came back inconsistent', () => {
-    // ⛔ Not a hole to fill with a fallback: `number`'s faces disagree by
-    // design (no-fixed-width on the cell, 0 in the summary footer) and the
-    // grouping policy keys on absent-vs-declared-0; `currency` resolves its
-    // cell's fraction digits from ISO 4217 minor units and can no longer
-    // declare this key at all (retired from the type, refused at parse).
+  it('declares NO width for number — ruled (5791809146, letter A′): natural precision, and it stays so', () => {
+    // ⛔ Not a hole to fill with a fallback, and not an open question: an
+    // absent `scale` on a `number` field means NO fixed width — the value's
+    // natural precision — as the platform's declared answer (maintainer ruling
+    // 5791809146, batch 215 item 2, letter A′). A face that prints `0` for it
+    // is the consumer defect, not this answer; grouping is `useGrouping`'s to
+    // decide, and its interim heuristic reads the DECLARED `scale`, never this.
     expect(resolveFieldScale({ type: 'number' })).toBeUndefined();
+  });
+
+  it('declares NO width for currency — the key is retired from the type', () => {
+    // `currency` resolves its cell's fraction digits from ISO 4217 minor units
+    // and can no longer declare this key at all (retired from the type,
+    // refused at parse).
     expect(resolveFieldScale({ type: 'currency' })).toBeUndefined();
   });
 
 
@@ -56,15 +56,26 @@
  * the ruling's own instruction each takes its own card with its readings rather
  * than a guessed default here:
  *
- * - `number` — the faces deliberately DISAGREE, and one of them load-bearingly.
- *   The cell renderer resolves absence to "no fixed width" (minimum 0 digits,
- *   maximum 20) while the grid summary footer and the metric widget resolve it
- *   to `0`; and the display-grouping policy keys on the very distinction a
- *   default would erase — a DECLARED `scale: 0` marks a discrete integer (a
- *   year, a fiscal period, an ordinal) and is rendered ungrouped, while an
- *   absent `scale` means "decimals unknown" and keeps its separators. Declaring
- *   `number ⇒ 0` would print every undeclared number field ungrouped: `2026`
- *   where the platform shows `2,026`.
+ * - `number` — ruled since, and not by a row here either: an absent `scale` on
+ *   a `number` field means NO fixed width — the value's natural precision —
+ *   and that is the platform's declared answer, ⛔ not an open question
+ *   (maintainer ruling 5791809146, batch 215 item 2, letter A′, 「215 同意」).
+ *   The census that sent it to its own card found the faces disagreeing: the
+ *   cell renderer resolved absence to "no fixed width" (minimum 0 digits,
+ *   maximum 20) while the grid summary footer and the metric widget resolved
+ *   it to `0`. The ruling makes the cell's answer the protocol's, and its
+ *   consumer half is objectui#9843: the footer and the widget drop their
+ *   private `?? 0` and read the width through {@link resolveFieldScale}, and a
+ *   computed result over a no-fixed-width column rounds to the widest decimal
+ *   count among the values that entered it — derived from the data, ⛔ never a
+ *   constant. Grouping is not this key's to decide:
+ *   `FieldSchema.useGrouping` decides, and the renderer's interim heuristic
+ *   for an absent `useGrouping` reads the DECLARED `scale` only — a declared
+ *   `scale: 0` marks a discrete integer (a year, a fiscal period, an ordinal)
+ *   and renders ungrouped — never a resolved width, so no answer from this
+ *   module moves a thousands separator. A `0` row stays refused: as a width it
+ *   would cut every undeclared number to an integer, and batch 194 refused
+ *   `number ⇒ 0` by name for printing `2026` where the platform shows `2,026`.
  * - `currency` — ruled since, and not by a row here: `scale` is RETIRED from
  *   the `currency` type (#19629, ruling 5791803339 letter B) and refused at
  *   parse, so a currency field declares no `scale` for this table to default.
@@ -81,8 +92,9 @@
  *   inline grid COLUMN's rounding of a computed result, not to a field's
  *   display width.
  *
- * ⛔ Neither reading is an argument for a `0` row: `number` still awaits its
- * own ruling, and `currency` no longer has a declaration to resolve.
+ * ⛔ Neither reading is an argument for a `0` row: `number`'s absent value is
+ * ruled to be no fixed width, and `currency` no longer has a declaration to
+ * resolve.
  *
  * ## Why the table is not exported
  *