@apliteni/apliteni-ui 0.8.0 → 0.8.1

package/README.md

@@ -105,7 +105,12 @@ import { DataTable, Modal } from '@apliteni/apliteni-ui/react';
 ```
 
 The source lives in [`react/`](./react) — a private workspace with its own build
-(tsup) and Storybook on port 6007. Details in [`react/README.md`](./react/README.md).
+(tsup) and Storybook on port 6007. When 6007 is taken Storybook moves to the next
+free port, so the root Storybook does not trust the number: it probes the range
+6007 can drift into and composes the first port that proves it is this workspace's
+Storybook. A stranger on the port is never composed — the "React components"
+section is absent instead, and the terminal says why. Details in
+[`react/README.md`](./react/README.md).
 
 ## Theming
 
@@ -147,7 +152,7 @@ react/                   # React components — private workspace, built to reac
 
 ```bash
 npm install
-npm run storybook          # http://localhost:6006
+npm run storybook          # http://localhost:6006, or the next free port
 npm run build-storybook    # -> storybook-static/
 node site/build.mjs        # -> site/public/ (landing + kit.css + /storybook)
 ```
@@ -156,7 +161,7 @@ The React components build and test through the workspace (`npm install` at the
 root covers them — there is no second install):
 
 ```bash
-npm run storybook -w react   # http://localhost:6007
+npm run storybook -w react   # http://localhost:6007, or the next free port
 npm test -w react            # vitest
 npm run build                # tsup -> react/dist/ (also runs on prepare)
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apliteni/apliteni-ui",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "workspaces": [
     "react"
   ],

package/react/README.md

@@ -41,6 +41,17 @@ npm run storybook -w react   # http://localhost:6007
 npm run build                # tsup -> react/dist/
 ```
 
+6007 is a request, not a promise: if something else already holds it, Storybook
+walks upward to the next free port. The root Storybook composes these components
+by following that drift — it probes 6007 through 6016 (the window Storybook's own
+port-finder searches) and takes the first one whose `index.json` lists every story
+file this workspace has on disk. A stranger on the port fails that check and is
+never shown under "React components"; the section is simply absent, and the root
+Storybook's terminal says which ports it tried and what it found.
+
+The probe runs once, while the root Storybook boots. Start this one afterwards and
+you have to restart the root Storybook before it appears.
+
 The bare `@apliteni/apliteni-ui` specifier in this source resolves to the kit itself
 once installed. In the repo there is no copy to resolve to, so `kit-alias.ts` points
 vitest and Storybook straight at `../src/` — which is why the class-name parity tests

package/src/styles/nav.css

@@ -75,7 +75,9 @@
 .ui-nav__item.is-current .ui-nav__ic svg { opacity: 1; stroke: var(--accent); }
 .ui-nav__label { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
 
-.ui-nav__item.is-danger { color: var(--pink); }
+/* Destructive row (sign out, revoke). Quiet at rest, --pink once the pointer
+   reaches it — same two-step as .ui-btn--danger and .ui-dropdown__item.is-danger. */
+.ui-nav__item.is-danger { color: var(--muted); }
 .ui-nav__item.is-danger:hover { background: var(--glow-pink); color: var(--pink); }
 .ui-nav__item.is-disabled { color: var(--muted); opacity: 0.55; cursor: default; pointer-events: none; }
 

package/src/styles/table.css

@@ -68,6 +68,19 @@
 .ui-table--zebra th { border-bottom-width: 2px; }
 .ui-table--zebra td { border-bottom: 0; }
 .ui-table--zebra tbody tr:nth-child(even) td { background: var(--surface-2); }
+/* The stripe is full-bleed on purpose — the hover note above inset the hover fill for
+ * #71 and deliberately left the ledger stripe alone. But full-bleed only reads right if
+ * the end cells are inset from the tint's own edge, and the base rhythm does not inset
+ * them: `.ui-table td` sets `padding-left: 0`. Only `--dense` supplied the inset, so a
+ * `--zebra` table composed WITHOUT `--dense` put the first cell's content at exactly
+ * x=0 of the stripe. `DataTable` is that composition — it writes `ui-table
+ * ui-table--hover ui-table--zebra` and no `--dense` — so its select-all and per-row
+ * checkboxes sat flush against the tint with a measured 0px gap.
+ * Header and body are inset together, or the columns stop lining up. */
+.ui-table--zebra th:first-child,
+.ui-table--zebra td:first-child { padding-left: 12px; }
+.ui-table--zebra th:last-child,
+.ui-table--zebra td:last-child { padding-right: 12px; }
 .ui-table--zebra.ui-table--hover tbody tr:hover td,
 .ui-table--zebra tbody tr:hover td { background: color-mix(in srgb, var(--accent) 8%, transparent); }