anentrypoint-design 0.0.382 → 0.0.384

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anentrypoint-design",
-  "version": "0.0.382",
+  "version": "0.0.384",
   "description": "247420 design system SDK — webjsx + modified ripple-ui, single-file ESM bundle for reproducible use of the AnEntrypoint design.",
   "type": "module",
   "main": "./dist/247420.js",

package/src/components/files-modals.js

@@ -159,7 +159,7 @@ function Modal({ onClose, kind = '', head, headClass = '', headAttrs = {}, body,
 // mutation is visible at the point of action, inside the focus trap — not a
 // sibling stuck in page flow behind the fixed backdrop).
 function modalError(error) {
-    return error ? h('p', { class: 'ds-modal-error field-error', role: 'alert' }, String(error)) : null;
+    return error ? h('p', { class: 'ds-modal-error', role: 'alert' }, String(error)) : null;
 }
 
 // `error` renders inside .ds-modal-body (role=alert, error tone). `busy`

package/src/components/overlay-primitives/menus.js

@@ -109,7 +109,11 @@ export function MenuButton({ trigger, items = [], selected, onSelect, onRetry, p
                     : h('button', {
                         key: it.id || i, type: 'button', role: 'menuitemradio',
                         'aria-checked': it.id === selected ? 'true' : 'false',
-                        class: 'ov-menubutton-item' + (it.disabled ? '' : ''),
+                        // No disabled modifier class: editor-primitives.css styles
+                        // .ov-menubutton-item[aria-disabled="true"] directly, so the
+                        // aria attribute below is both the semantics and the hook.
+                        // (This was a ternary whose branches returned the same string.)
+                        class: 'ov-menubutton-item',
                         'aria-disabled': it.disabled ? 'true' : 'false',
                         tabindex: '-1', onclick: () => select(it),
                     },

package/src/css/app-shell/base.css

@@ -21,7 +21,7 @@ button, input, select, textarea { font: inherit; }
   left: 0;
   background: var(--accent);
   color: var(--accent-fg);
-  padding: 8px 16px;
+  padding: var(--space-2) var(--space-3);
   text-decoration: none;
   /* Must outrank every layer of chrome once focused, or the first Tab press
      lands on a control hidden behind the sticky header (was z-index:100,
@@ -36,6 +36,35 @@ button, input, select, textarea { font: inherit; }
   outline: var(--focus-w) solid var(--focus-color);
   outline-offset: var(--focus-offset);
 }
+/* Visually-hidden but still in the accessibility tree. Emitted by Row() (the
+   rail status word), FilterBar()/FileGrid() (aria-live result counts) and
+   form-primitives' required marker — all of which shipped BEFORE this rule
+   existed anywhere the app shell loads. The only other definitions live in
+   app-surfaces.css (pre-scoped to `.ds-247420`, so it never reaches a kit that
+   does not mount that root) and editor-primitives.css (a separate opt-in
+   <link>), which left every app-shell consumer rendering screen-reader-only
+   text VISIBLY the moment it passed `rail`/`resultCount`.
+   Deliberately NOT `display:none` / `visibility:hidden` / `width:0`: those
+   remove the node from the accessibility tree too, which defeats the entire
+   purpose — the text exists only for AT. The clip + 1px box is what keeps it
+   announced while occupying no visible area.
+   `margin: -1px` is OFF-SCALE ON PURPOSE — it is not rhythm, it is one half of
+   the canonical visually-hidden idiom: the negative margin cancels the 1px box
+   so the clipped element contributes zero layout. Snapping it to a --space-*
+   rung would reintroduce a measurable gap. `clip` is deprecated but retained
+   alongside `clip-path` for older AT/browser pairs that ignore the latter. */
+.sr-only {
+  position: absolute;
+  width: 1px;
+  height: 1px;
+  padding: 0;
+  margin: -1px;
+  overflow: hidden;
+  clip: rect(0, 0, 0, 0);
+  clip-path: inset(50%);
+  white-space: nowrap;
+  border: 0;
+}
 body {
   background: var(--bg);
   color: var(--fg);
@@ -124,6 +153,30 @@ h4, .t-h4 { font-family: var(--ff-display); font-size: var(--fs-h4); line-height
 .ds-prose h1 { font-size: clamp(34px, 5.4cqi, 64px); margin-bottom: var(--space-3); }
 .ds-prose h2 { margin: var(--space-6) 0 var(--space-3); }
 .ds-prose h3 { margin: var(--space-5) 0 var(--space-2); font-size: var(--fs-lg); font-weight: 600; }
+/* Closing line of an article ("end. reply by opening a pr."), set off from the
+   body it terminates. Quieter and smaller than the prose around it: it takes
+   the mono face and the --fg-3 tone the house uses for ancillary voices
+   (.t-micro, .dim), so the endnote reads as chrome around the article rather
+   than a final paragraph of it. The --space-5 lead does the "set off" — it
+   breaks the paragraph rhythm so the eye registers the piece has ended before
+   reading the words; margin-bottom:0 overrides .ds-prose p's --space-4 so the
+   article does not end on dead space.
+   Lives here, beside the rest of the .ds-prose family, NOT in gm-prose.css:
+   the blog kit that uses this class links only colors_and_type.css +
+   app-shell.css, so a rule in that separately-<link>-ed export would be exactly
+   as undefined as the class was before. Sized at --fs-xs, not the --fs-micro
+   label rung: this is a readable sentence with a link in it, not a micro-label.
+   The link inherits .ds-prose a's --accent-ink treatment (a readable TEXT tone;
+   the bare --accent fill is ~1.07:1 on paper) — deliberately not re-stated. */
+.ds-prose .ds-prose-endnote,
+.ds-prose-endnote {
+  margin-top: var(--space-5);
+  margin-bottom: 0;
+  font-family: var(--ff-mono);
+  font-size: var(--fs-xs);
+  line-height: var(--lh-base);
+  color: var(--fg-3);
+}
 
 .dim { color: var(--fg-3); }
 

package/src/css/app-shell/hero-content.css

@@ -254,6 +254,16 @@ table tr.clickable:focus-visible td { background: var(--bg-2); }
    Changelog
    ============================================================ */
 .ds-changelog-row {
+  /* The !important is load-bearing and was empirically confirmed so -- do not
+     remove it on a specificity argument. A changelog row carries three tracks
+     (date, version, message) where a plain .row carries two, and the responsive
+     blocks in responsive.css legitimately rewrite .row's template at several
+     breakpoints. Those blocks are later in the cascade, so at tablet width the
+     two-track override wins on source order and collapses the version column:
+     measured live, removing this flag changes the computed template from
+     "120.75px 77.625px 70.125px" to "103.5px 0px 165px" -- a zero-width column
+     and the version silently gone. Scoping to .app does not help, because the
+     competing rules would need to be scoped in lockstep. */
   grid-template-columns: minmax(110px, 14ch) minmax(60px, 9ch) minmax(0, 1fr) !important;
 }
 .ds-changelog-ver {

package/src/css/app-shell/kits-appended.css

@@ -806,3 +806,22 @@
   .cursor-blink { animation: ds-cursor-blink 1s step-end infinite; }
   @keyframes ds-cursor-blink { 50% { opacity: 0; } }
 }
+
+/* == appended: panel width modifier == */
+/* .panel.panel-inline-wide — a width-capped inline note panel. Companion to
+   the .panel-inline / .panel-wide modifiers in panel-row.css: those two change
+   the panel's SURFACE (tonal fill / chrome-stripped), this one changes only
+   its MEASURE, so it composes with either. Introduced when ui_kits/docs's
+   `[!] note` panel traded `style="max-width:640px"` for a class (the inline-
+   style sweep) but never got a rule written, leaving that panel to run the
+   full column width. 640px is the note measure, deliberately narrower than
+   --measure-narrow (760px): the aside is meant to read as a set-aside block
+   against the surrounding prose, not to match its column. It is a literal
+   rather than a new token because it has exactly one consumer — promote it to
+   --measure-note the moment a second surface wants the same cap.
+   `margin-right: auto` (not `margin: 0 auto`) keeps the panel left-aligned to
+   the prose it interrupts and preserves .panel's own --space-4 stack margin. */
+.panel.panel-inline-wide {
+  max-width: 640px;
+  margin-right: auto;
+}

package/src/css/app-shell/responsive.css

@@ -53,16 +53,28 @@
   .panel-body { padding: var(--space-2); overflow-x: auto; -webkit-overflow-scrolling: touch; }
   .panel-body > table { min-width: 100%; }
 
-  .row {
-    grid-template-columns: minmax(0, 1fr) auto !important;
+  /* Scoped to the `.app` shell so this wins on SPECIFICITY (0,2,0) rather than
+     on an !important flag. Three rules would otherwise beat a bare `.row`
+     (0,1,0) here: `.row.row-nocode` (0,2,0, panel-row.css) out-specifies it,
+     and the `@media(481-1024)` + `@media(max-width:768px)` `.row` rules later
+     in THIS file win on source order (a media query adds no specificity).
+     `.app` is safe to require: `.app-body`/`.row` only ever render inside it
+     (single call site, shell.js AppShell). */
+  .app .row {
+    grid-template-columns: minmax(0, 1fr) auto;
     gap: var(--space-2); padding: var(--space-2-75) var(--space-3);
-    row-gap: var(--space-1) !important;
+    row-gap: var(--space-1);
   }
   .row .sub { grid-column: 1 / -1; order: 3; }
   .row .title { font-size: var(--fs-sm); }
   /* Changelog carries 3 children: give date+ver line one, message wraps below
-     (the generic 2-col .row override staggers it into an implicit row). */
-  .ds-changelog-row { grid-template-columns: minmax(70px, 10ch) minmax(0, 1fr) !important; }
+     (the generic 2-col .row override staggers it into an implicit row).
+     Needs (0,3,0) to clear BOTH the `.app .row` rule directly above and
+     `.ds-changelog-row`'s own !important base in hero-content.css — an
+     !important base can only be beaten by another !important, so this one
+     stays until that upstream flag is removed (hero-content.css is outside
+     this change's scope). */
+  .app .row.ds-changelog-row { grid-template-columns: minmax(70px, 10ch) minmax(0, 1fr) !important; }
   .ds-changelog-row .title { grid-column: 1 / -1; }
 
   /* Buttons */
@@ -150,12 +162,20 @@
    Container Query Responsive (720px and below)
    ---------------------------------------------------------------------- */
 @container (max-width: 760px) {
-  .app-body { grid-template-columns: 1fr !important; }
+  /* `.app`-scoped for specificity, not an !important flag: the bare `.app-body`
+     (0,1,0) was out-specified by `.app-body.no-side` (0,2,0) in topbar.css, so
+     a sidebar-less shell kept its base template. `.app .app-body` is (0,2,0)
+     and lands later in source, beating both topbar.css rules on merit. */
+  .app .app-body { grid-template-columns: 1fr; }
   .app-side-shell { border-right: 0; border-bottom: 1px solid var(--rule); }
   .app-topbar nav { font-size: var(--fs-xs); gap: var(--space-2-75); }
-  .row { grid-template-columns: minmax(0, 1fr) auto !important; row-gap: var(--space-1) !important; }
+  /* Same (0,2,0) lift as the 480px block above — clears `.row.row-nocode` and
+     the later `@media` `.row` rules in this file without a flag. */
+  .app .row { grid-template-columns: minmax(0, 1fr) auto; row-gap: var(--space-1); }
   .row .sub { grid-column: 1 / -1; order: 3; }
-  .ds-changelog-row { grid-template-columns: minmax(70px, 10ch) minmax(0, 1fr) !important; }
+  /* (0,3,0) + !important: still required to beat `.ds-changelog-row`'s
+     !important base in hero-content.css (see the 480px block). */
+  .app .row.ds-changelog-row { grid-template-columns: minmax(70px, 10ch) minmax(0, 1fr) !important; }
   .ds-changelog-row .title { grid-column: 1 / -1; }
 }
 

package/src/css/app-shell/responsive2-workspace.css

@@ -10,8 +10,16 @@
    even on a wide desktop. Drawer/scrim/toggle are absolute (anchored to .app), so
    they overlay the window, not the page. */
 @container (max-width: 900px) {
-  .app-body,
-  .app-body.no-side { grid-template-columns: 1fr !important; }
+  /* `.app`-scoped for specificity instead of an !important flag. The bare
+     `.app-body` half of this list is (0,1,0) and was out-specified by
+     `.app-body.no-side` (0,2,0) in topbar.css; scoping lifts both halves to
+     (0,2,0)/(0,3,0), which also lands later in source than topbar.css, so the
+     drawer collapse wins on merit. `.app` is guaranteed: `.app-body` is
+     emitted only as a direct child of `.app` (single call site, shell.js
+     AppShell), and this @container query already requires `.app` as its
+     container ancestor. */
+  .app .app-body,
+  .app .app-body.no-side { grid-template-columns: 1fr; }
   .app-side-shell {
     position: absolute;
     /* Full-height overlay drawer: the merged .app-chrome wraps and its real
@@ -36,9 +44,13 @@
   .app-side-shell.open,
   .app-side.open,
   .app-body.side-open .app-side-shell { transform: translateX(0); }
+  /* No flags needed: the ONLY other rule that touches these properties is the
+     `.app-side` base in topbar.css, which already sets `flex-direction: column`
+     and never sets `flex-wrap` (nowrap is the initial value anyway). This rule
+     is equal-specificity and later in source, so it wins unaided. */
   .app-side {
-    flex-direction: column !important;
-    flex-wrap: nowrap !important;
+    flex-direction: column;
+    flex-wrap: nowrap;
     gap: var(--space-2);
     padding: var(--space-3);
     font-size: var(--fs-sm);

package/src/css/app-shell/states-interactions.css

@@ -56,11 +56,16 @@ button:disabled, [disabled] {
   animation: spinner-rotate 0.8s linear infinite;
 }
 
-/* Error state */
+/* Error state.
+   No !important: the only rule in the kit that also resets a matching element's
+   border-color is the bare-control base below (`textarea:where(:not(.input))`
+   et al, which use the `border: 0` shorthand). Those selectors are (0,0,1) —
+   the :where() guard adds nothing — so every selector in this list out-specifies
+   them on merit, and specificity beats the later source position. */
 .error, [data-state="error"],
 .row.error, input.error,
 textarea.error {
-  border-color: var(--warn) !important;
+  border-color: var(--warn);
   background-color: color-mix(in oklab, var(--warn) 6%, var(--bg));
 }
 .error::placeholder { color: color-mix(in oklab, var(--warn) 60%, var(--fg-3)); }
@@ -576,7 +581,17 @@ input[type="password"]:not(:placeholder-shown) + .input-clear {
 .skip-to-main:focus { top: 10px; }
 
 /* Reduced motion preferences — scoped to the DS surface so it doesn't reach
-   into and neutralize the host document's own motion. */
+   into and neutralize the host document's own motion.
+   The !important flags here are LOAD-BEARING and must not be "cleaned up":
+   `.ds-247420 *` / `.app *` is only (0,1,0) — the universal selector adds
+   nothing — yet it has to defeat every animation/transition declaration in the
+   kit, many of which are strictly more specific. Concrete rules it would
+   otherwise lose to: `.ds-dropzone.dragover` (0,2,0, files.css),
+   `.ds-upload-bar.indeterminate .ds-upload-fill` (0,3,0, files.css),
+   `.list-item.drag-after::after` (0,2,1, this file). Raising this selector to
+   out-specify an open-ended set of future component rules is not possible, so
+   the flag is the only correct mechanism — this is a WCAG 2.3.3 guarantee,
+   not a stylistic preference. */
 @media (prefers-reduced-motion: reduce) {
   .ds-247420 *, .app * {
     animation-duration: 0.01ms !important;
@@ -584,7 +599,9 @@ input[type="password"]:not(:placeholder-shown) + .input-clear {
     transition-duration: 0.01ms !important;
   }
   /* Kill the residual paint frame of looping skeleton/shimmer placeholders and
-     give reduced-motion users a steady placeholder fill instead. */
+     give reduced-motion users a steady placeholder fill instead.
+     Also load-bearing: `.skeleton` is (0,1,0) and must override
+     `.ds-session-row-skeleton .ds-skel` (0,2,0), which sets its own shimmer. */
   .skeleton, .ds-skeleton, .ds-session-row-skeleton .ds-skel {
     animation: none !important;
     background: var(--bg-2) !important;

package/src/css/app-shell/topbar.css

@@ -201,7 +201,11 @@ body.canvas-host { background: transparent !important; }
   border-radius: var(--r-pill);
 }
 /* The lime active pill is the sidebar's one accent moment; its own count
-   chip rides the ink-on-accent pair instead of a second competing hue. */
+   chip rides the ink-on-accent pair instead of a second competing hue.
+   The bare --accent here is deliberate and is NOT the usual accent-as-text
+   defect: the chip's own background is --accent-fg (ink), so this is the
+   INVERTED pair -- lime on ink, which is the high-contrast direction. Only
+   accent-coloured text on a normal background needs --accent-ink. */
 .app-side a.active .count {
   background: color-mix(in oklab, var(--accent-fg) 82%, transparent);
   color: var(--accent);