@godxjp/ui 18.6.0 → 18.8.0

package/dist/tokens/components/shell.css

@@ -81,10 +81,21 @@
   --topbar-height: auto;
   --topbar-inset: 0px;
   --topbar-gap: var(--space-2);
-  /* At compact desktop/tablet widths the docked sidebar leaves too little inline room for three
-   * intrinsically-sized clusters. The package hides the optional center slot before it can cover
-   * the breadcrumb/title or end utilities. Consumers may opt back into another display strategy
-   * (for example `flex`) once their center content has its own compact presentation. */
+  /* ⚠ THIS KNOB DELETES CONTENT AT 1100px AND BELOW — read before you ship a center slot.
+   * At compact desktop/tablet widths the docked sidebar leaves too little inline room for three
+   * intrinsically-sized clusters, so the package hides the optional center slot before it can
+   * cover the breadcrumb/title or end utilities (gh#244). The default is `none`, which means a
+   * global search trigger placed in `center` is INVISIBLE from 1100px down — including on every
+   * phone — unless the consumer opts back in. That default arrived in 18.6.0 and removed the slot
+   * for consumers who never changed a line of their own code (gh#12); it stays because the
+   * overlap it prevents is a real defect and flipping a shipped default twice is worse than
+   * documenting it once, but it is a DECISION, not an accident:
+   *
+   *   :root { --topbar-center-compact-display: flex; }   ← restore the slot at every width
+   *
+   * Opt back in only once the center content has a compact presentation of its own (an icon-only
+   * search trigger, a collapsing field). A page-local media query is the anti-pattern this knob
+   * replaces. */
   --topbar-center-compact-display: none;
   --org-switcher-trigger-height: 2.75rem;
   --org-switcher-trigger-padding-x: var(--space-2);
@@ -181,6 +192,18 @@
   --auth-shell-device-card-max-width: 23.75rem;
   --auth-shell-device-main-padding: 1rem;
   --auth-shell-device-main-padding-mobile: 0.9375rem 0.3125rem;
+  /* CODE FIELD measure — the preset owns it (gh#12). A device grant is the one canonical flow whose
+   * PRIMARY control is the code field, so leaving it on the generic square --otp-slot-size made the
+   * preset own the page but not its own subject: two 4-slot `appearance="grouped"` boxes rendered
+   * 146x38 (4 x the canonical 36px control tier + the 1px group border) against a 112x54 artboard.
+   * These are the per-slot boxes that ADD UP to that artboard group:
+   *   inline  27.5px x 4 + 2 x 1px group border = 112px
+   *   block   52px       + 2 x 1px group border =  54px
+   * Literal artboard lengths, like every other preset measure here — they must not drift with
+   * --scaling. A service that groups its code differently overrides --otp-slot-inline-size /
+   * --otp-slot-block-size on its own field; the generic square knob is untouched everywhere else. */
+  --auth-shell-device-otp-slot-inline-size: 1.71875rem;
+  --auth-shell-device-otp-slot-block-size: 3.25rem;
 
   /* Context-selection preset — 25rem card measure on desktop/tablet, edge-to-edge on mobile
    * (0 inline gutter) with a 16px rhythm between the intro, the card and the remember row. */
@@ -201,6 +224,43 @@
   --auth-shell-recovery-main-padding: 1rem;
   --auth-shell-recovery-main-padding-mobile: 0.9375rem;
 
+  /* Registration preset (gh#256) — the canonical sign-up measure. Two things make it structurally
+   * different from every preset above, and both are the reason it could not be expressed by
+   * re-using `login`:
+   *
+   *  1. LONG-FORM SCROLLING. A registration card is the tallest surface in the hosted-identity set
+   *     (name · email · password · confirm · strength meter · consent · submit · provider row), and
+   *     a vertically CENTRED tall card clips its own top on a short viewport — the top overflows
+   *     above the scroll origin and becomes unreachable. So the column is start-aligned and the
+   *     block-start inset becomes ordinary page padding the user can scroll past.
+   *  2. FOOTER CLEARANCE. The legal/consent footer must never be flush against the submit button
+   *     at the end of a long scroll, so the block-end inset is a knob of its own rather than
+   *     mirroring the block-start one.
+   *
+   * The 360px form measure and the 15px mobile inline gutter match the canonical Login flow exactly
+   * (22.5rem card, x=15 at 390 ⇒ width=360), so a user moving sign-in → sign-up on a phone never
+   * sees the surface jump. */
+  --auth-shell-registration-card-max-width: 22.5rem;
+  /* Block-start offsets are DERIVED from the canonical SCR-002 artboard, not chosen: the card
+   * anchors at y=284 (1440x900) and y=274 (390x844), and the column is
+   *   card y = padding-block-start + identity slot + stack gap
+   * so 284 - 112 - 20 = 152px (9.5rem) and 274 - 112 - 20 = 142px (8.875rem). Like every canonical
+   * screen in this family the page passes NO brand bar (the mark lives INSIDE the column as
+   * AuthIdentity), so `main` starts at the viewport top and the offset is the whole anchor. */
+  --auth-shell-registration-main-padding-block-start: 9.5rem;
+  --auth-shell-registration-main-padding-block-start-mobile: 8.875rem;
+  --auth-shell-registration-main-padding-inline: 1rem;
+  --auth-shell-registration-main-padding-inline-mobile: 0.9375rem;
+  /* Footer clearance — the gap the legal footer keeps below the end of a long form. */
+  --auth-shell-registration-main-padding-block-end: 3rem;
+  --auth-shell-registration-main-padding-block-end-mobile: 2rem;
+  --auth-shell-registration-card-stack-gap: 1.25rem;
+  /* Fixed identity track, the same 112px `login` proved (gh#237). Without it the card anchor moves
+   * with the title/requester line count — measured here at 82.69px for one wrapped requester — so
+   * the canonical y above would hold for exactly one copy length and drift for every other. The
+   * slot absorbs absent / one-line / two-line identity content instead. */
+  --auth-shell-registration-identity-slot-block-size: 7rem;
+
   /* Labelled auth divider geometry. */
   --auth-shell-divider-gap: 0.625rem;
   --auth-shell-divider-label-font-size: 0.6875rem;

package/dist/tokens/semantic/layout.css

@@ -83,6 +83,19 @@
    * page moves. 11rem = 176px, i.e. the control ends flush with the compact page gutter. */
   --page-header-extra-measure: 11rem; /* 176px */
 
+  /* Inline gap between the `<h1>` and the PageHeader `meta` slot (a status Badge, a record ID) when
+   * they share the title band (gh#255). Only consumed when `meta` is passed — a header without it
+   * emits no band wrapper at all, so no existing page moves. */
+  --page-header-meta-gap: var(--space-inline-sm);
+
+  /* PageHeader `loading` placeholders (gh#255). The title/subtitle elements wear the shared
+   * `.ui-skeleton-block` skin, so they need only a MEASURE and a block size — a service retunes the
+   * pending band's proportions here instead of per page. */
+  --page-title-placeholder-measure: 14rem; /* 224px */
+  --page-title-placeholder-block-size: 1.5em;
+  --page-subtitle-placeholder-measure: 22rem; /* 352px */
+  --page-subtitle-placeholder-block-size: 1.25em;
+
   /* Bounded page MEASURE (gh#245 / gh#247) — the shared inline cap applied to the page HEADER and
    * BODY together, so the header `extra` action ends on the same edge as the body surface (the
    * `variant="narrow"` complaint: it caps only `.ui-page-body`, leaving the header action out at

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@godxjp/ui",
-  "version": "18.6.0",
-  "godxUiMcp": "18.6.0",
+  "version": "18.8.0",
+  "godxUiMcp": "18.8.0",
   "type": "module",
   "packageManager": "pnpm@10.29.1",
   "pnpm": {