@lotics/ui 44.7.0 → 44.7.1

package/docs/composition.md

@@ -376,6 +376,13 @@ a dashboard. Card stat rails use `KPICard`.
 ## Numbers, money, dates
 
 - Free-standing numerals: `<Text tabular>` — always.
+- **A column states its unit ONCE — which is only possible if it holds ONE unit.** State it in the
+  header band and leave the cells bare. The corollary is the one that bites: a label/value list
+  whose rows are a date range, a sum of money and a COUNT has no single unit to state, so each
+  value carries its own — and a count sharing a column with a currency at the same size, weight
+  and right edge is unreadable however well the labels are worded, because the eye reads a column
+  of figures as one series. Where the mixed units are parallel across many rows, they are not one
+  column at all: give each its own, and the band names both.
 - **Money**: `formatMoney(n)` from `@lotics/ui/format_money` (`compact` abbreviates values
   ≥ 1,000,000 for strip captions). **Warning:** the full-value path formats via `Intl`, whose
   output separates the currency symbol with a non-breaking space (the compact path uses a plain
@@ -1223,6 +1230,13 @@ column of them. Dropped to `xs` and lightened past `muted` it stops being legibl
 reading as a caption that lost its value — small type is not the same as quiet type. The active
 SORTED column steps up in ink, never in weight; semibold belongs to the heading ladder.
 
+**A fixed column `width` is sized for the LONGEST locale, not the one you typed it in.** Every
+header is a translated string, and the same label runs half again as long in Vietnamese as in
+English — so a width measured against the source truncates the header in the language the app
+actually ships in, on a column the reader was told to check. It fails silently in review because
+the reviewer reads the source locale. Size against the longest translation, or give the column
+`flex` and let it take what it needs.
+
 **Sentence case, in the table header too.** The heading ramp already bans all-caps and names it
 the #1 templated tell; `Table` and `SortHeader` were uppercasing every column label in every app,
 which is the loudest possible version of the thing the rule exists to stop. Removing the case

package/docs/reviewing.md

@@ -222,6 +222,16 @@ spacing distinguishes them.
   offsets is the signature. Fix by bounding the child that varies — never with a cross-axis knob
   (it moves the content and leaves the chrome), and never by resizing the CONTAINER, which changes
   both terms and leaves the spread.
+- **A VARIABLE-width leading slot destroys the column behind it.** A row's lead is sized for an
+  icon; put a chip, a badge or a name in it and every row's title starts at a different x. Collect
+  one repeated cell's `left` down the rows — more than one distinct value and the column does not
+  exist, however aligned each row looks on its own. The spread is small enough to read as
+  sloppiness rather than as a defect, which is why it survives review; the fix is a fixed-width
+  lead, or a register, where columns make it impossible.
+- **Every numeric column: is its unit named anywhere, and is it ONE unit?** Collect the leaf values
+  sharing a right edge, with their size and weight. Identical treatment across values that are not
+  the same KIND of thing — a count beside a currency — is the signature, and the labels beside them
+  do not rescue it. → [composition.md](./composition.md) §"Numbers, money, dates".
 - **A slot holding another component's part must be sized by that component's constant** — a
   24px mark in an 18px column sits 3px outside the surface.
 - **A row beat belongs to the PAGE** — collect every row primitive's height on one screen before

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "44.7.0",
+  "version": "44.7.1",
   "type": "module",
   "exports": {
     "./vite": {