anentrypoint-design 0.0.464 → 0.0.466

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anentrypoint-design",
-  "version": "0.0.464",
+  "version": "0.0.466",
   "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/css/app-shell/base.css

@@ -152,7 +152,12 @@ h4, .t-h4 { font-family: var(--ff-display); font-size: var(--fs-h4); line-height
 .t-mega    { font-family: var(--ff-display); font-size: var(--fs-mega); line-height: 0.92;            letter-spacing: var(--tr-tighter); font-weight: 700; margin: 0; }
 
 .t-display { font-family: var(--ff-display); font-weight: 600; letter-spacing: var(--tr-tight); }
-.t-mono    { font-family: var(--ff-mono); }
+/* Explicit weight, not relying on inherited normal: --ff-mono's stack (Menlo,
+   Consolas, ui-monospace) can resolve to a variable-font fallback on some
+   platforms whose default instance isn't the 400 weight, rendering "body ·
+   16px regular" visibly bold despite its own label -- pin the weight so the
+   sample matches what it claims regardless of which font in the stack loads. */
+.t-mono    { font-family: var(--ff-mono); font-weight: 400; }
 .t-body    { font-family: var(--ff-body); }
 
 /* House small-label voice, in two sizes. Every declaration here is sourced

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

@@ -92,7 +92,12 @@
   border-color: var(--rule);
 }
 .ds-file-row:active { transform: translateY(1px); }
-.ds-file-row.active { background: var(--accent-tint); border-color: var(--accent); }
+/* file-grid's own header/caption both claim NEVER A BORDER -- border-color
+   here silently broke that promise for exactly the row it's meant to call
+   out (the row a screenshot/manual test would actually look at). Selected
+   state stays legible via the tint alone; border-color stays transparent so
+   the base rule's promise holds for every row, active or not. */
+.ds-file-row.active { background: var(--accent-tint); }
 .ds-file-row[data-file-type="dir"]      { border-left-width: 3px; border-left-color: var(--accent); }
 .ds-file-row[data-file-type="image"],
 .ds-file-row[data-file-type="video"],
@@ -427,9 +432,14 @@
 }
 .ds-error-banner:hover { background: color-mix(in oklab, var(--warn) 20%, var(--bg)); }
 
-/* Dropzone */
+/* Dropzone — a tonal target, not a dashed-border affordance (preview/
+   dropzone.html's own header/caption both describe this: "NO DASHED
+   BORDERS" / "tonal panel that swaps to --panel-select on dragover"). A
+   solid hairline plus the idle->dragover background swap is the actual
+   design; dashed was this system's OTHER "drop target" vocabulary
+   (.panel-docs, kits-appended.css) leaking in here by copy-paste. */
 .ds-dropzone {
-  border: var(--bw-rule) dashed var(--rule);
+  border: var(--bw-rule) solid var(--rule);
   border-radius: var(--r-3); background: var(--bg);
   transition: border-color var(--dur-base) var(--ease), background var(--dur-base) var(--ease);
 }

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

@@ -69,7 +69,12 @@
      still fits a narrow column, and a 116px ceiling between the two tiers.
      Snapping to either changes the hero's whole optical weight. */
   font-size: clamp(40px, 9cqi, 116px);
-  line-height: 0.96; letter-spacing: var(--tr-tighter);
+  /* 0.96 let ascenders/descenders visibly touch between wrapped lines at the
+     upper end of this clamp (measured on "the creative department of the
+     internet" at the 116px ceiling) -- 1.02 keeps the tight, no-air display
+     feel this title wants while clearing enough vertical room that letters
+     stop colliding. */
+  line-height: 1.02; letter-spacing: var(--tr-tighter);
   margin: 0; max-width: 20ch; text-wrap: balance;
 }
 .ds-hero-body {
@@ -292,11 +297,18 @@ table {
      (was 12/14 x 16 => ~43px rows). Density scales the vertical padding. */
   border-radius: var(--r-0); overflow: hidden;
 }
+/* Panel heads / KPI labels / table headers were all identical uppercase-
+   tracked-mono weight (600), so a page with several of these side by side
+   (a dashboard) reads as one flat volume with no anchor -- the most
+   repetitive, least-singular label (a column header, one of many per
+   table) drops to a lighter 500 with slightly tighter tracking, keeping the
+   system's uppercase-mono voice but giving panel titles (still 600) a real
+   step up as the "read this first" tier. */
 table th {
   text-align: left;
   padding: calc(var(--space-2) * var(--density)) var(--space-2-75);
-  font-size: var(--fs-tiny); font-weight: 600;
-  color: var(--fg-3); text-transform: uppercase; letter-spacing: var(--tr-caps);
+  font-size: var(--fs-tiny); font-weight: 500;
+  color: var(--fg-3); text-transform: uppercase; letter-spacing: calc(var(--tr-caps) * 0.7);
   background: var(--bg-2);
 }
 /* letter-spacing adds trailing space AFTER the last glyph too, but the table's

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

@@ -390,12 +390,21 @@
   gap: var(--space-1-75, 6px);
 }
 /* Table() scroll containment — wide tables scroll inside their own box,
-   never the page body. */
+   never the page body. overflow-x:auto alone works but gives no visible cue
+   that a table is wider than its box (macOS overlay scrollbars stay hidden
+   until an active hover/scroll gesture) -- columns beyond the fold read as
+   simply missing rather than reachable. An always-visible thin scrollbar
+   track makes the overflow legible without a gesture first. */
 .ds-table-wrap {
   overflow-x: auto;
   -webkit-overflow-scrolling: touch;
   max-width: 100%;
+  scrollbar-width: thin;
+  scrollbar-color: var(--rule-strong) transparent;
 }
+.ds-table-wrap::-webkit-scrollbar { height: 8px; }
+.ds-table-wrap::-webkit-scrollbar-thumb { background: var(--rule-strong); border-radius: var(--r-pill, 999px); }
+.ds-table-wrap::-webkit-scrollbar-track { background: transparent; }
 .ds-table-wrap > table { min-width: 100%; }
 /* Sortable column headers (Table's opt-in sortable prop) — a docstudio-cue
    addition: color stays neutral at rest (this is a structural control, not a

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

@@ -30,13 +30,19 @@
 }
 .btn { background: var(--bg-2); color: var(--fg); border-color: var(--rule); }
 .btn:hover { background: var(--bg-3); color: var(--fg); transform: translateY(-1px); box-shadow: var(--shadow-1); }
-/* Primary CTA — the electric lead as a solid editorial block; hover inverts to
-   an ink block with the lead as text, a confident two-tone flip. */
+/* Primary CTA — the brand green as a solid editorial block; hover inverts to
+   an ink block with green text, a confident two-tone flip. Uses --green
+   (the site's own #247420 identity color, dark-mode-retuned to --green's
+   ink-safe #5CBF52 rather than --accent/--acid, which a prior contrast-driven
+   restyle deliberately flattened to a neutral gray for --accent's OTHER
+   consumers (nav active state, focus rings, etc) -- .btn-primary needed the
+   brand color back for click-hierarchy without undoing that restyle
+   elsewhere. --on-color (#fff) clears AA on both light and dark --green. */
 .btn-primary {
-  background: var(--accent); color: var(--accent-fg);
+  background: var(--green); color: var(--on-color);
   font-weight: 700;
 }
-.btn-primary:hover { background: var(--fg); color: var(--accent-ink); transform: translateY(-1px); box-shadow: var(--shadow-2); }
+.btn-primary:hover { background: var(--fg); color: var(--green); transform: translateY(-1px); box-shadow: var(--shadow-2); }
 .btn-ghost { background: transparent; color: var(--fg); box-shadow: inset 0 0 0 2px var(--fg); }
 .btn-ghost:hover { background: var(--fg); color: var(--bg); transform: translateY(-1px); }
 .btn:active, .btn-primary:active, .btn-ghost:active { transform: translateY(1px); box-shadow: none; }

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

@@ -26,10 +26,16 @@ tr.clickable:focus-visible {
    :disabled pseudo-class, so a disabled link-styled button relies entirely
    on this class selector for its visual treatment (aria-disabled + tabindex
    are set in JS; this is the paired CSS half). */
+/* opacity:0.6 alone barely separated from an active .btn-primary against a
+   busy background -- close enough in dark mode that users clicked disabled
+   buttons expecting them to work. grayscale flattens any color signal (no
+   more "still looks clickable-green") and the steeper opacity drop reads as
+   unmistakably inert at a glance, not just slightly dimmed. */
 .btn:disabled, .btn-primary:disabled, .btn-ghost:disabled,
 .btn.is-disabled, .btn-primary.is-disabled, .btn-ghost.is-disabled,
 button:disabled, [disabled] {
-  opacity: 0.6;
+  opacity: 0.45;
+  filter: grayscale(60%);
   cursor: not-allowed;
   pointer-events: none;
 }
@@ -350,7 +356,13 @@ textarea::placeholder {
   transform: rotate(-2deg);
   white-space: nowrap;
 }
-.stamp.ink { background: var(--ink); border-color: var(--ink); color: var(--paper); }
+/* border-color previously matched background exactly (var(--ink) on both) --
+   same class of bug as the colors-core "paper" swatch: a border drawn in the
+   identical color as its own fill is invisible, so the ink-toned stamp was
+   the one variant on the page missing its box outline. --paper reads as a
+   visible ring against the ink fill (paper-on-ink is this token pair's
+   whole reason to exist), matching every other .stamp variant's contrast. */
+.stamp.ink { background: var(--ink); border-color: var(--paper); color: var(--paper); }
 .stamp.acid { background: var(--accent); border-color: var(--accent-ink); color: var(--accent-ink); }
 .stamp.purple { border-color: var(--purple-2); color: var(--purple-2); }
 .stamp.mascot { border-color: var(--mascot); color: var(--mascot-deep); }
@@ -365,6 +377,11 @@ textarea::placeholder {
   border: 2px solid var(--fg);
   border-radius: var(--r-hair);
   background: transparent; color: var(--fg);
+  /* .stamp's own caption claims the rubber-stamp motif is "always rotated
+     slightly" -- .btn-stamp is the same visual face as an interactive
+     <button> (preview/stamps-lore.html's second row) and had no rotation at
+     all, breaking that claim for every stamp in that row. */
+  transform: rotate(-2deg);
   transition: background var(--dur-snap) var(--ease), color var(--dur-snap) var(--ease);
 }
 .btn-stamp:hover { background: var(--panel-hover); }
@@ -382,11 +399,20 @@ hr.rule, hr.rule-double, hr.rule-dotted {
 }
 hr.rule { border-top: 1px solid var(--rule); }
 hr.rule-double { border-top: 4px double var(--rule-strong); }
-hr.rule-dotted { border-top: 1px dotted var(--rule-strong); }
-
-/* Hairline-only text input — no box, no fill. A single bottom rule that
-   thickens to 2px on focus, matching the row/rule zero-border aesthetic
-   instead of a browser-default boxed field. */
+/* 1px was indistinguishable from .rule -- border-style:dotted needs enough
+   width to actually draw a gap between dots; below ~2px (esp. at DPRs where
+   1px resolves to a sub-pixel value like 0.8px) Chrome collapses it to a
+   solid line, which is exactly what preview/rules.html's report caught live. */
+hr.rule-dotted { border-top: 2px dotted var(--rule-strong); }
+
+/* Hairline-only text input — no full box, no permanent fill. A single bottom
+   rule that thickens to 2px on focus, matching the row/rule zero-border
+   aesthetic instead of a browser-default boxed field. A completely flat,
+   static hairline reads as a static label rather than an editable control
+   at a glance (no cue at rest, nothing on hover) -- the very faint permanent
+   wash plus a stronger hover tint below signal "this is a field" without
+   reverting to the boxed/filled chrome the hairline design deliberately
+   moved away from. */
 .input {
   display: block; width: 100%; box-sizing: border-box;
   /* appearance:none alone is not enough: with color-scheme:dark set on the
@@ -400,11 +426,13 @@ hr.rule-dotted { border-top: 1px dotted var(--rule-strong); }
   color-scheme: normal;
   border: 0; border-bottom: 1px solid var(--rule-strong);
   border-radius: var(--r-0);
-  background: transparent;
+  background: color-mix(in oklab, var(--fg) 2.5%, transparent);
   box-shadow: none;
   padding: var(--space-2) var(--space-1);
   font: inherit; color: var(--fg);
+  transition: background var(--dur-snap) var(--ease), border-color var(--dur-snap) var(--ease);
 }
+.input:hover { background: color-mix(in oklab, var(--fg) 5%, transparent); }
 /* Touch floor for the BASE input. Several specific inputs already carried this
    (ds-file-filter-input, ds-modal-input, ds-term-input) but the primitive every
    form actually uses did not, so a plain field measured 34px under a coarse

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

@@ -160,7 +160,20 @@ body.canvas-host { background: transparent !important; }
    `minmax(0, 1fr)` — a real height the sidebar can overflow once bins +
    labels + more exceed it. Without this the extra rows were silently chopped
    at the viewport edge with no way to reach them. */
-.app-side-shell { background: var(--bg); overflow-y: auto; min-height: 0; }
+/* .app-side-shell and .app-main (below) are two INDEPENDENT scroll regions
+   side by side -- correct by design (a sidebar nav and a main panel each own
+   their own overflow), but with default invisible/overlay OS scrollbars a
+   user hovering the boundary has no visual cue which region the wheel will
+   scroll, or that there even are two scrollable zones rather than one page
+   scroll. Thin always-visible scrollbar tracks make each region's own scroll
+   ownership legible without changing the (correct) two-region architecture. */
+.app-side-shell {
+  background: var(--bg); overflow-y: auto; min-height: 0;
+  scrollbar-width: thin; scrollbar-color: var(--rule-strong) transparent;
+}
+.app-side-shell::-webkit-scrollbar { width: 8px; }
+.app-side-shell::-webkit-scrollbar-thumb { background: var(--rule-strong); border-radius: var(--r-pill, 999px); }
+.app-side-shell::-webkit-scrollbar-track { background: transparent; }
 .app-body { display: grid; grid-template-columns: var(--sidebar-width) minmax(0, 1fr); grid-template-rows: minmax(0, 1fr); align-items: stretch; align-content: stretch; flex: 1; min-height: 0; }
 .app-body.no-side { grid-template-columns: minmax(0, 1fr); }
 /* When there is no sidebar, the empty side-shell must not occupy a grid row,
@@ -268,6 +281,15 @@ body.canvas-host { background: transparent !important; }
 /* Reserve the scrollbar track so routes with/without overflow don't shift
    the layout horizontally when the bar appears. */
 .app-main { scrollbar-gutter: stable; }
+/* Same visible-scroll-ownership rationale as .app-side-shell above -- makes
+   this the visually distinct SECOND independent scroll region rather than
+   an invisible-scrollbar mystery next to the sidebar. */
+.app-main {
+  scrollbar-width: thin; scrollbar-color: var(--rule-strong) transparent;
+}
+.app-main::-webkit-scrollbar { width: 8px; }
+.app-main::-webkit-scrollbar-thumb { background: var(--rule-strong); border-radius: var(--r-pill, 999px); }
+.app-main::-webkit-scrollbar-track { background: transparent; }
 /* Jump-target anchors clear the inner-scroll top edge (no chrome overlap,
    but a little breathing room when deep-linked within .app-main). */
 .app-main [id] { scroll-margin-top: var(--space-4); }
@@ -358,5 +380,16 @@ body.canvas-host { background: transparent !important; }
   color: var(--fg-3);
 }
 .dateline span { white-space: nowrap; overflow: hidden; text-overflow: ellipsis; min-width: 0; }
-.dateline .spread { flex: 1 1 auto; min-width: var(--space-3); }
+/* The spreader itself only ever set flex-basis -- an empty div with no
+   background renders as blank space, not the "dotted spreader" the preview
+   page's own caption describes. border-bottom (not background-image) keeps
+   the dots crisp at 1px without a repeating-gradient banding artifact. */
+.dateline .spread {
+  flex: 1 1 auto; min-width: var(--space-3); align-self: stretch;
+  display: flex; align-items: center;
+}
+.dateline .spread::after {
+  content: ''; flex: 1 1 auto;
+  border-bottom: var(--bw-hair, 1px) dotted var(--rule-strong);
+}
 

package/src/kits/os/theme.css

@@ -829,6 +829,7 @@ html.ds-247420 { touch-action: pan-x pan-y; overscroll-behavior: none; -webkit-t
   display: flex; align-items: center; justify-content: center;
   pointer-events: none;
 }
+.tb-sess-empty[hidden] { display: none; }
 .tb-sess-empty-card {
   pointer-events: auto;
   background: var(--bg);

package/src/kits/os/wm.css

@@ -134,6 +134,8 @@
 .wm-win.wm-min .wm-body,
 .wm-win.wm-min .wm-resize { display: none; }
 
+.wm-win.wm-min { display: none; }
+
 .wm-win.wm-max {
     left: 0 !important;
     top: 0 !important;