@lotics/ui 43.7.0 → 43.7.1

package/examples/tpl_record.tsx

@@ -2931,20 +2931,19 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418", openSection
           divider above the section for every section before it. */}
       {/* The header band sits ABOVE the stack, on the canvas beat — it is the
           record's IDENTITY, not a section, so the 56px between-sections rhythm
-          (and, in scroll mode, the hairline that comes with it) does not apply.
-          Every condition it used to announce now lives on the field it concerns,
-          with a dot on the rail saying which section to look in. */}
+          (and, in scroll mode, its hairline) does not apply. A condition belongs
+          on the FIELD it concerns, with a dot on the rail naming the section to
+          look in — never announced up here away from what it is about. */}
       <View style={{ flex: 1, minWidth: 0, gap: 28 }}>
         {/* The record's own ACTS live here, beside its identity — not inside a
-            section. Dropping a file is something you do TO THE RECORD, but its
-            only affordance used to sit in the Files section, which scoped the
-            discoverability to that section: from anywhere else on the page
-            (or from 3,975px above it) nothing said the record took files at
-            all, and a whole-record drop target nobody can see is an
-            accelerator, never an entry point. The Files register keeps its own
-            Add — a register's Add belongs under its register — this is the
-            record-level way in. A template composition for now; it earns a kit
-            slot on RecordSummary at its second consumer. */}
+            section. Dropping a file is something you do TO THE RECORD, so an
+            affordance for it that lives only in the Files section is scoped to
+            that section: from anywhere else on a long page nothing says the
+            record takes files at all, and a whole-record drop target nobody can
+            see is an accelerator, never an entry point. The Files register keeps
+            its own Add — a register's Add belongs under its register — and this
+            is the record-level way in. A template composition for now; it earns a
+            kit slot on RecordSummary at its second consumer. */}
         <View style={{ flexDirection: "row", alignItems: "flex-start", gap: 16 }}>
           <View style={{ flex: 1, minWidth: 0 }}>
             {/* The SUBJECT leads, the key goes under it. A reader talks about
@@ -3165,31 +3164,17 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418", openSection
             />
           ) : (
             <>
-              {/* AN ENTRY, NOT A LOG LINE — and that distinction is the whole
-                  reason this stopped being a `Timeline`.
-
-                  `Timeline` puts its label INSIDE the row's press target. That
-                  is right for an event ("Stage changed to Won") whose text is
-                  derived and read-only. It is wrong here, because the gist is
-                  the one thing on an entry a person WROTE, and text inside a
-                  button can never be edited where it sits. Four repairs came out
-                  of working around that — the verbs moved off the row, the label
-                  learned to un-clamp, the body's copy of the gist came out, and
-                  the Edit verb ended up a scroll away from the sentence it
-                  edits. They were never independent: each one was the
-                  arrangement pushing back.
-
-                  So the gist is not a label. It is a RESIDENT field — always
-                  editable, in place, no mode and no Edit button, the same as
-                  every other authored value on this record. The old argument
-                  against a resident editor here ("the gist is already the row's
-                  label, so it renders the sentence twice") disappears the moment
-                  it stops being one.
-
-                  What is left is the shape every comment UI converged on: a
-                  metadata header, the prose under it, the row's own actions at
-                  the TOP RIGHT beside the text they act on, and the heavy
-                  artifacts behind their own disclosure. */}
+              {/* AN ENTRY, NOT A LOG LINE — which is why this is not a `Timeline`.
+                  `Timeline` puts its label INSIDE the row's press target, right
+                  for a derived read-only event ("Stage changed to Won") and wrong
+                  for a sentence a person WROTE: text inside a button cannot be
+                  edited where it sits.
+
+                  So the gist is a RESIDENT field — always editable in place, no
+                  mode, no Edit button, like every other authored value here. The
+                  shape every comment UI converges on: a metadata header, the prose
+                  under it, the row's actions at the TOP RIGHT beside the text they
+                  act on, and heavy artifacts behind their own disclosure. */}
               <View style={{ gap: 20 }}>
                 {(showAllActivity ? activity : activity.slice(0, ACTIVITY_FOLD)).map((a) => (
                   <ActivityEntryRow
@@ -3712,52 +3697,25 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418", openSection
         </Section>
         </View>
 
-        {/* PHOTOS — a second SET, and therefore the other SURFACE.
-
-            Files above is a row LIST because a shipping document is identified by
-            its NAME: a PDF thumbnail is a grey page identical to every other grey
-            page, so a grid of them is a wall of one tile. A photo is identified
-            by its CONTENT — `IMG_4471.jpg` tells nobody anything — so the tile IS
-            the identity and a grid puts twelve on screen at once.
-            (AGENTS.md: documents get a LIST, images get a GRID.)
-
-            BOTH SURFACES SHOW THE WHOLE COLLECTION — they are two LENSES over
-            one set, not two sets. Files answers "what is on this record" in a
-            scannable column; Photos answers "what did it LOOK like" at a glance.
-            A reader who guesses wrong still finds the artifact instead of
-            concluding it was never filed, and nobody has to know a file's FORMAT
-            before they know where to look for it.
-
-            The grid used to filter to `image/*`. That made the split a fact about
-            MIME rather than about reading, and it put the signed delivery note in
-            a different section from the photos of the same hand-over — while this
-            very comment promised that the odd `.docx` among forty phone photos
-            would stay in the grid. It could not: the filter forbade what the
-            sentence described. `FileThumbnail` already renders a non-image as a
-            doc tile (badge + filename), so nothing had to be built — only the
-            filter that hid it had to go.
-
-            THE COST IS REAL AND DELIBERATE: every file now appears twice. The
-            trade is that duplication is cheap to skim past, whereas an artifact
-            filed under the wrong lens looks like an artifact that was never
-            filed. A record whose attachments are overwhelmingly paperwork should
-            drop the grid entirely rather than carry a wall of identical tiles —
-            the choice is per-record-TYPE, made once, not per file.
-
-            Ordering follows the collection, so a record heavy in documents leads
-            this grid with grey tiles. If that reads badly for your record type,
-            sort images first rather than reinstating the filter.
-
-            The tiles are mixed by construction now, so the FIXTURE has to be
-            mixed too — a grid of eight JPGs never once renders the doc tile it
-            has always been able to render, which is how the gap survived.
-
-            The ADD rides the heading row, right edge, exactly as it does on Files
-            and Fees — a section's add sits in the same spot whether the section
-            holds nought or forty. Note it is a plain `Button` + `pickFiles`, not
-            `FilesEditorUpload`: that verb reads the `FilesEditor` context, and the
-            heading is OUTSIDE the editor by construction, so a compound's own
-            upload button can never reach the one place the law puts it. */}
+        {/* PHOTOS — two LENSES over ONE set, not two sets. Files answers "what is
+            on this record" in a scannable column; this answers "what did it LOOK
+            like" at a glance. (List for documents, grid for images: AGENTS.md.)
+
+            BOTH show the WHOLE collection, unfiltered. A reader who guesses wrong
+            still finds the artifact instead of concluding it was never filed, and
+            nobody has to know a file's FORMAT before knowing where to look. The
+            cost is real: every file appears twice. Duplication is cheap to skim
+            past; an artifact filed under the wrong lens reads as missing.
+
+            Ordering follows the collection, so a document-heavy record leads with
+            grey tiles — sort images first if that reads badly, and drop the grid
+            entirely for a record type that is overwhelmingly paperwork. That
+            choice is per record TYPE, made once, never per file.
+
+            The add is a plain `Button` + `pickFiles`, NOT `FilesEditorUpload`:
+            that verb reads the `FilesEditor` context and the heading row sits
+            outside the editor by construction, so the compound's own upload
+            button cannot reach the one place the law puts it. */}
         <View onLayout={nav.register("photos")}>
         <Section>
           <SectionHeading>
@@ -4147,26 +4105,16 @@ export function TplRecord({ chrome = "page", code = "RC-2026-0418", openSection
                             <InlineTextInput value={f.note} onSave={persist((v: string) => patchFee(f.id, { note: v }))} placeholder="Add a note…" accessibilityLabel="Fee note" />
                           </DetailRow>
                         </DetailTable>
-                        {/* The destructive verb, LEFT — the peek footer's
-                            convention, which is the kit's. It replaces the
-                            DrawerFooter that used to pin it.
-
-                            Solid `danger`, which is the destructive convention
-                            page-wide (composition rule 9) — not a text-weight act.
-                            A quiet destructive verb had been tried here and the
-                            surface-less rung is gone: an act now always carries a
-                            control, and only NAVIGATION is underlined text. The trash
-                            glyph stays off — "Remove fee" already names the object,
-                            which is the safeguard the icon was only decorating.
-
-                            NO Divider. Every hairline a `Table` draws is
-                            full-bleed (the row `Divider`s carry no padding, the
-                            header band's border spans its whole box), so one
-                            inset by ROW_GUTTER puts two hairline lengths in the
-                            same vertical run — and it would be saying twice what
-                            the expanded row's own wash already says. The row
-                            wrapper is required, not decoration: a `Button` alone
-                            in a column View stretches to full width. */}
+                        {/* The destructive verb, LEFT — the peek footer's convention.
+                            Solid `danger` per composition rule 9; no trash glyph,
+                            because "Remove fee" already names the object the icon
+                            was only decorating.
+
+                            NO Divider. Every hairline a `Table` draws is full-bleed,
+                            so one inset by ROW_GUTTER puts two hairline lengths in
+                            the same vertical run — and it repeats what the expanded
+                            row's wash already says. The row wrapper IS required: a
+                            `Button` alone in a column View stretches full width. */}
                         <View style={{ flexDirection: "row" }}>
                           <Button title="Remove fee" color="danger" onPress={() => deleteFee(f)} />
                         </View>

package/package.json

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