@lotics/ui 28.0.0 → 28.2.0

package/MIGRATION.md

@@ -4,6 +4,40 @@ Breaking changes, newest first — normally per major, plus the rare minor that
 anyway (recorded under its exact version). The current contract lives in `AGENTS.md` + `docs/`;
 this file exists only to move an app from one release to the next.
 
+## 28.2.0 — `SubsectionHeadingTitle` takes a `description`
+
+Additive; nothing to change. The heading ramp's three rungs are meant to carry the SAME slots
+and differ only in type size — `description` was missing from the middle one, so a group that
+needed a muted line under its title had to borrow the section rung above it or hand-roll a
+`Text` off the ramp.
+
+It matters most where a GROUP receives something. A `FileDropTarget`-wrapped region shows no
+dropzone, so `AGENTS.md` requires the heading to name the drag and paste paths — and a surface
+with several PEER file regions (per-kind photo buckets, each its own target, because nothing in
+a dropped file says which bucket it belongs to) carries those regions at subsection rung:
+
+```tsx
+<SubsectionHeading>
+  <SubsectionHeadingTitle description="Kéo, dán hoặc bấm để thêm ảnh">Ảnh hạ</SubsectionHeadingTitle>
+</SubsectionHeading>
+```
+
+The rung is unchanged (`###`, lg semibold, level 3) — only the slot is new.
+
+## 28.1.0 — `ChecklistItem` can announce more than its title
+
+Additive; nothing to change. `accessibilityLabel` overrides the row's accessible name, which
+still defaults to `title`. It exists for a surface carrying one checklist PER person, party or
+period, where the same row labels repeat and only the headings between them tell the copies
+apart — a reader moving control to control does not get those headings. Put the distinguishing
+noun in the accessible name, not in `title`, so the visible rows stay free of what the heading
+above already says.
+
+Also fixed here: **`TASK_TEXT_INSET` was cut in 28.0.0 without a replacement named.** It is
+`CONTROL_TEXT_INSET` from `@lotics/ui/control_surface` — the same 9 (1px border + 8px padding),
+and always about a CONTROL's text rather than a step's, which is why it did not follow the rest
+of `task` into `checklist`.
+
 ## 28.0.0 — `task` and `pipeline` merge into `checklist`
 
 Two families had converged on one anatomy: a ring, a title, a value beside it, a muted note, a

package/docs/catalog.md

@@ -399,7 +399,8 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
 - **`spacing`** — the `SPACE` scale + `SpaceToken`.
 - **`control_surface`** — `CONTROL_HEIGHT` (40), `CONTROL_RADIUS` (10), `CONTROL_TEXT_INSET`
   (9 — how far a control insets its OWN text: 1px border + 8px padding; anything that must line
-  up with a control's WORDS rather than its box carries it, and `TASK_TEXT_INSET` IS it),
+  up with a control's WORDS rather than its box carries it — a caption under an inline editor,
+  a note under a figure — rather than a hand-measured 8),
   `FOCUS_RING` (a 2px OUTSET ring, so a container that CLIPS — any `ScrollView` — has to
   keep padding on an edge a focusable child sits against, or the ring shears off on the
   one interaction it signals; the padding still comes off the 8-grid, the ring is only
@@ -450,13 +451,17 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   (16, fixed), no body component. `SectionHeadingTitle` is ALWAYS `##` (xl semibold;
   `weight="medium"` opt-down only) + `info` for an ⓘ provenance popover after the title,
   same as `CardHeaderTitle.info`. `SubsectionHeadingTitle` is the `###` lg-semibold level-3
-  title of a named group inside a section (same `info` ⓘ affordance as the section title) —
-  heading-row siblings ride its right edge. **A section's ADD is one of those siblings** — a
+  title of a named group inside a section (same `info` ⓘ AND `description` slots as the section
+  title) — heading-row siblings ride its right edge. Its `description` is what a files
+  SUBSECTION uses to name its drag/paste paths: a `FileDropTarget`-wrapped region shows no
+  dropzone, and a surface with several peer file regions (per-kind photo buckets, each its own
+  target) carries that line at THIS rung, not the section above it. **A section's ADD is one of those siblings** — a
   `primary` `Button` beside the title, rendered whether the collection is empty or full, never
   under the rows it extends and never repeated in the `EmptyState`
   (composition.md § The add-placement law). `DialogSectionHeadingTitle` is the `####`
   md-semibold rung with the SAME `icon`/`description`/`info` slots as the section title, so a
-  dialog surface loses only the type size, never an affordance. The heading ramp is FIXED:
+  dialog surface loses only the type size, never an affordance. **`description` is on every
+  rung** — the ramp's slots do not vary by level; only the type size does. The heading ramp is FIXED:
   `#` xxl / `##` xl / `###` lg / `####` md, no size props.
 - **`section_stack`** — `SectionStack`, `SubsectionStack` — stacks that own the
   between-block law, skipping null children: `SectionStack` = a fixed 56px beat + a hairline
@@ -1295,8 +1300,12 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   today, so a run filled in after the fact needs the correction in reach — and `ChecklistField`
   for a value with NO other home (a portal login created at that step, unreachable otherwise).
   `ChecklistItem.meta` is two words on the title's row; prose that grows is a `ChecklistNote`,
-  which owns its line. Worked screens: `tpl_record` § Progress (connected, grouped) and its
-  document desk (unconnected set).
+  which owns its line. A row ANNOUNCES its `title`; `ChecklistItem.accessibilityLabel` overrides
+  that for the one case the title cannot carry alone — a surface with one checklist PER person,
+  party or period, where the same labels repeat and only the headings between them separate the
+  copies, which a reader moving control to control never hears. The distinguishing noun goes in
+  the accessible name, never the title, or every visible row repeats its own heading. Worked
+  screens: `tpl_record` § Progress (connected, grouped) and its document desk (unconnected set).
 - **`stepper`** — `Stepper` + `Step` — done/current/upcoming/warning/complete progress on a
   track (horizontal) or spine (vertical); compound `<Step status>children` OR data
   `steps[]`+`current`; **navigable** via `Step.onPress` (both orientations — the whole step

package/docs/composition.md

@@ -64,8 +64,11 @@ restyle a heading level per-page.
   stays ABSOLUTE — this is one more fixed size, never a `size`/`compact` knob on a rung above.
 - **Subsection title** — the level BELOW a section on a long record surface: `Subsection` ›
   `SubsectionHeading` › `SubsectionHeadingTitle` (`###` — lg semibold, with the same `info` ⓘ
-  affordance as `SectionHeadingTitle`; siblings — a `Badge`, a
-  `SectionHeadingMeta`, an action — ride the heading row's right edge). Sibling subsections stack
+  and `description` slots as `SectionHeadingTitle`; siblings — a `Badge`, a
+  `SectionHeadingMeta`, an action — ride the heading row's right edge). Reach for its
+  `description` when the GROUP is what receives something — a files subsection wrapped in its
+  own `FileDropTarget` has to name drag and paste itself, since a wrapped region shows no zone
+  and the section above it may hold several such groups. Sibling subsections stack
   in a **`SubsectionStack`** (a fixed 32px beat; no margins, no hand-rolled dividers).
   It is SPACE-ONLY while the groups are SHORT — the titles carry the grouping and hairlines
   belong to the SECTION level, one rule per altitude — and takes `divided` once the groups run

package/package.json

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

package/src/checklist.tsx

@@ -190,6 +190,19 @@ export interface ChecklistItemProps extends StepPositional {
   /** The row's name. Doubles as the ring's accessible name — the ring carries no
    *  visible label of its own, so the text rides beside it. */
   title: string;
+  /**
+   * Override that accessible name. Defaults to `title`, which is right whenever
+   * the title identifies the row on its own.
+   *
+   * Reach for it when the SAME titles repeat down a surface and only their
+   * surroundings tell them apart — one checklist per person, per party, per
+   * period, each listing the same rows. A reader moving control to control gets
+   * the names without the headings between them, so three rows all announcing
+   * "Đơn đăng ký" are three controls they cannot tell apart. Put the
+   * distinguishing noun in here, NOT in `title`: the heading above already says
+   * it, and repeating it in every visible row is noise for everyone else.
+   */
+  accessibilityLabel?: string;
   /** Ticked. */
   done?: boolean;
   /** The row the reader is waiting on — medium weight, so a run full of ticks
@@ -222,6 +235,7 @@ export interface ChecklistItemProps extends StepPositional {
 /** ONE ROW — the level that carries the ticks. */
 export function ChecklistItem({
   title,
+  accessibilityLabel,
   done,
   current,
   onToggle,
@@ -235,7 +249,7 @@ export function ChecklistItem({
     <Step
       status={done ? "done" : current ? "current" : "upcoming"}
       onToggle={onToggle}
-      accessibilityLabel={title}
+      accessibilityLabel={accessibilityLabel ?? title}
       {...positional}
     >
       <View style={{ gap: 6 }}>

package/src/section_heading.tsx

@@ -87,6 +87,17 @@ export function SubsectionHeading(props: SubsectionHeadingProps) {
 
 export interface SubsectionHeadingTitleProps {
   children: React.ReactNode;
+  /**
+   * Muted line under the title, as on the rungs either side of this one.
+   *
+   * The ramp carries the same slots at every rung, and this was the one gap in
+   * it. It matters most for a group that RECEIVES something: a files region
+   * wrapped in a `FileDropTarget` shows no dropzone, so drag and paste are
+   * invisible unless the heading names them — and a surface with several peer
+   * file regions (per-kind photo buckets, each its own drop target) puts them at
+   * THIS rung, where the prescribed line previously had nowhere to sit.
+   */
+  description?: string;
   /** Heading rank. Defaults to 3 — one level under `SectionHeadingTitle`'s 2. */
   level?: HeadingLevel;
   /** An ⓘ popover after the title — a short "what this is / where it came from"
@@ -98,14 +109,25 @@ export interface SubsectionHeadingTitleProps {
  * xl section title and above the md/sm body. Grows to push siblings (a
  * `SectionHeadingMeta`, a `Badge`, an action) to the right edge. */
 export function SubsectionHeadingTitle(props: SubsectionHeadingTitleProps) {
-  const { children, level = 3, info } = props;
+  const { children, description, level = 3, info } = props;
   const words = useLoticsLocale();
+  // Same anatomy as `SectionHeadingTitle` one rung down: the title row keeps its
+  // own `flexDirection: "row"` so `info` sits beside the text, and the column
+  // wrapper carries the `flex: 1` that lets a heading row push meta to its right
+  // edge. Without the wrapper the description would land on the title's LINE.
   return (
-    <View style={{ flex: 1, flexDirection: "row", alignItems: "center", gap: 6 }}>
-      <Text level={level} size="lg" weight="semibold">
-        {children}
-      </Text>
-      {info ? <InfoPopover text={info} accessibilityLabel={words.sectionHeading.info} /> : null}
+    <View style={{ flex: 1, gap: 2 }}>
+      <View style={{ flexDirection: "row", alignItems: "center", gap: 6 }}>
+        <Text level={level} size="lg" weight="semibold">
+          {children}
+        </Text>
+        {info ? <InfoPopover text={info} accessibilityLabel={words.sectionHeading.info} /> : null}
+      </View>
+      {description ? (
+        <Text color="zinc-500" size="sm">
+          {description}
+        </Text>
+      ) : null}
     </View>
   );
 }