@naeil/ui 0.9.0 → 0.11.0

package/dist/source/components/naeil-standalone-messages.d.ts

@@ -0,0 +1,11 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { ReactNode } from 'react';
+import { NaeilHeaderLocale } from './naeil-header-data.js';
+
+/** Only the standalone compatibility entry includes all three small dictionaries. */
+declare function NaeilStandaloneMessages({ locale, children }: {
+    locale: NaeilHeaderLocale;
+    children: ReactNode;
+}): react_jsx_runtime.JSX.Element;
+
+export { NaeilStandaloneMessages };

package/dist/source/components/naeil-standalone-messages.js

@@ -0,0 +1,13 @@
+"use client";
+import { jsx } from "react/jsx-runtime";
+import en from "../naeil-locale/messages/en.json";
+import ko from "../naeil-locale/messages/ko.json";
+import ja from "../naeil-locale/messages/ja.json";
+import { NaeilMessagesProvider } from "./naeil-messages-context.js";
+const messages = { en: en.naeil, ko: ko.naeil, ja: ja.naeil };
+function NaeilStandaloneMessages({ locale, children }) {
+  return /* @__PURE__ */ jsx(NaeilMessagesProvider, { locale, messages: messages[locale], children });
+}
+export {
+  NaeilStandaloneMessages
+};

package/dist/source/i18n/routing.d.ts

@@ -1,5 +1,5 @@
 import * as next_dist_shared_lib_app_router_context_shared_runtime from 'next/dist/shared/lib/app-router-context.shared-runtime';
-import * as next_navigation from 'next/navigation';
+import * as next_dist_client_components_redirect_error from 'next/dist/client/components/redirect-error';
 import * as next_intl_navigation from 'next-intl/navigation';
 import * as url from 'url';
 import * as react from 'react';
@@ -31,8 +31,6 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     style?: react.CSSProperties | undefined;
     title?: string | undefined | undefined;
     locale?: string | undefined;
-    onError?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
-    children?: react.ReactNode;
     ref?: react.Ref<HTMLAnchorElement> | undefined;
     prefix?: string | undefined | undefined;
     key?: react.Key | null | undefined;
@@ -42,12 +40,10 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     passHref?: boolean | undefined;
     prefetch?: boolean | "auto" | null | undefined;
     legacyBehavior?: boolean | undefined;
-    onMouseEnter?: React.MouseEventHandler<HTMLAnchorElement> | undefined;
-    onTouchStart?: React.TouchEventHandler<HTMLAnchorElement> | undefined;
-    onClick?: React.MouseEventHandler<HTMLAnchorElement> | undefined;
     onNavigate?: ((event: {
         preventDefault: () => void;
     }) => void) | undefined;
+    transitionTypes?: string[] | undefined;
     download?: any;
     hrefLang?: string | undefined | undefined;
     media?: string | undefined | undefined;
@@ -104,7 +100,6 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     is?: string | undefined | undefined;
     exportparts?: string | undefined | undefined;
     part?: string | undefined | undefined;
-    tw?: string | undefined;
     "aria-activedescendant"?: string | undefined | undefined;
     "aria-atomic"?: (boolean | "true" | "false") | undefined;
     "aria-autocomplete"?: "none" | "inline" | "list" | "both" | undefined | undefined;
@@ -158,6 +153,8 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     "aria-valuemin"?: number | undefined | undefined;
     "aria-valuenow"?: number | undefined | undefined;
     "aria-valuetext"?: string | undefined | undefined;
+    href: string | url.UrlObject;
+    children?: react.ReactNode;
     dangerouslySetInnerHTML?: {
         __html: string | TrustedHTML;
     } | undefined | undefined;
@@ -177,20 +174,21 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     onFocusCapture?: react.FocusEventHandler<HTMLAnchorElement> | undefined;
     onBlur?: react.FocusEventHandler<HTMLAnchorElement> | undefined;
     onBlurCapture?: react.FocusEventHandler<HTMLAnchorElement> | undefined;
-    onChange?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onChangeCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
+    onChange?: react.ChangeEventHandler<HTMLAnchorElement, Element> | undefined;
+    onChangeCapture?: react.ChangeEventHandler<HTMLAnchorElement, Element> | undefined;
     onBeforeInput?: react.InputEventHandler<HTMLAnchorElement> | undefined;
-    onBeforeInputCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onInput?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onInputCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onReset?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onResetCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onSubmit?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onSubmitCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onInvalid?: react.FormEventHandler<HTMLAnchorElement> | undefined;
-    onInvalidCapture?: react.FormEventHandler<HTMLAnchorElement> | undefined;
+    onBeforeInputCapture?: react.InputEventHandler<HTMLAnchorElement> | undefined;
+    onInput?: react.InputEventHandler<HTMLAnchorElement> | undefined;
+    onInputCapture?: react.InputEventHandler<HTMLAnchorElement> | undefined;
+    onReset?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
+    onResetCapture?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
+    onSubmit?: react.SubmitEventHandler<HTMLAnchorElement> | undefined;
+    onSubmitCapture?: react.SubmitEventHandler<HTMLAnchorElement> | undefined;
+    onInvalid?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
+    onInvalidCapture?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
     onLoad?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
     onLoadCapture?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
+    onError?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
     onErrorCapture?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
     onKeyDown?: react.KeyboardEventHandler<HTMLAnchorElement> | undefined;
     onKeyDownCapture?: react.KeyboardEventHandler<HTMLAnchorElement> | undefined;
@@ -244,6 +242,7 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     onWaitingCapture?: react.ReactEventHandler<HTMLAnchorElement> | undefined;
     onAuxClick?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onAuxClickCapture?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
+    onClick?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onClickCapture?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onContextMenu?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onContextMenuCapture?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
@@ -267,6 +266,7 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     onDropCapture?: react.DragEventHandler<HTMLAnchorElement> | undefined;
     onMouseDown?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onMouseDownCapture?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
+    onMouseEnter?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onMouseLeave?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onMouseMove?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
     onMouseMoveCapture?: react.MouseEventHandler<HTMLAnchorElement> | undefined;
@@ -284,6 +284,7 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     onTouchEndCapture?: react.TouchEventHandler<HTMLAnchorElement> | undefined;
     onTouchMove?: react.TouchEventHandler<HTMLAnchorElement> | undefined;
     onTouchMoveCapture?: react.TouchEventHandler<HTMLAnchorElement> | undefined;
+    onTouchStart?: react.TouchEventHandler<HTMLAnchorElement> | undefined;
     onTouchStartCapture?: react.TouchEventHandler<HTMLAnchorElement> | undefined;
     onPointerDown?: react.PointerEventHandler<HTMLAnchorElement> | undefined;
     onPointerDownCapture?: react.PointerEventHandler<HTMLAnchorElement> | undefined;
@@ -325,7 +326,6 @@ declare const Link: react.ForwardRefExoticComponent<Omit<{
     onTransitionRunCapture?: react.TransitionEventHandler<HTMLAnchorElement> | undefined;
     onTransitionStart?: react.TransitionEventHandler<HTMLAnchorElement> | undefined;
     onTransitionStartCapture?: react.TransitionEventHandler<HTMLAnchorElement> | undefined;
-    href: string | url.UrlObject;
 }, "ref"> & react.RefAttributes<HTMLAnchorElement>>;
 declare const redirect: (args: {
     href: string | {
@@ -334,7 +334,7 @@ declare const redirect: (args: {
     };
     locale: string;
     forcePrefix?: boolean;
-}, type?: next_navigation.RedirectType | undefined) => never;
+}, type?: next_dist_client_components_redirect_error.RedirectType | undefined) => never;
 declare const usePathname: () => string;
 declare const useRouter: () => {
     push: (href: string | {
@@ -358,6 +358,8 @@ declare const useRouter: () => {
     back(): void;
     forward(): void;
     refresh(): void;
+    experimental_gesturePush?(href: string, options?: next_dist_shared_lib_app_router_context_shared_runtime.NavigateOptions): void;
+    bfcacheId: string;
 };
 declare const getPathname: (args: {
     href: string | {

package/dist/source/lib/ui-release.d.ts

@@ -1,5 +1,5 @@
 declare const uiRelease: {
-    readonly version: "0.9.0";
+    readonly version: "0.11.0";
     readonly contractVersion: "1";
 };
 

package/dist/source/lib/ui-release.js

@@ -1,4 +1,4 @@
-const uiRelease = { version: "0.9.0", contractVersion: "1" };
+const uiRelease = { version: "0.11.0", contractVersion: "1" };
 export {
   uiRelease
 };

package/dist/source/naeil-locale/messages/en.json

@@ -0,0 +1,78 @@
+{
+  "naeil": {
+    "header": {
+      "nav": {
+        "home": "Home",
+        "projects": "Projects",
+        "blog": "Blog",
+        "navigation": "Main navigation",
+        "menu": "Menu",
+        "closeMenu": "Close menu"
+      },
+      "theme": {
+        "switchToLight": "Switch to light theme",
+        "switchToDark": "Switch to dark theme"
+      },
+      "locale": {
+        "switchLabel": "Language"
+      },
+      "projects": {
+        "cc": {
+          "name": "Content Collector",
+          "description": "Automated content collection from RSS, YouTube, Reddit + AI summarization"
+        },
+        "pkm": {
+          "name": "PKM",
+          "description": "Personal knowledge management — document parsing, embeddings, semantic search"
+        },
+        "naeilUi": {
+          "name": "naeil-ui",
+          "description": "Minimal design system — OKLCH tokens, Tailwind v4, shadcn"
+        },
+        "sa": {
+          "name": "Sustainability Analyzer",
+          "description": "AI-powered ESG report analysis — PDF parsing, qualitative assessment, comparison tables"
+        },
+        "babyAgent": {
+          "name": "Baby Agent",
+          "description": "Parenting AI agent — LINE-based Q&A, records, reminders"
+        },
+        "status": {
+          "active": "Active",
+          "coming": "Coming Soon"
+        }
+      }
+    },
+    "account": {
+      "menu": "Account menu",
+      "account": "Account",
+      "login": "Log in",
+      "logout": "Log out",
+      "busy": "Logging out…"
+    },
+    "footer": {
+      "navigation": "Navigation",
+      "projects": "Projects",
+      "blog": "Blog",
+      "social": "Social",
+      "description": "Tomorrow starts here."
+    },
+    "locale": {
+      "names": {
+        "en": "English",
+        "ko": "한국어",
+        "ja": "日本語"
+      },
+      "pending": "Changing language…",
+      "failed": "The language could not be changed. Your work is still here.",
+      "retry": "Try again",
+      "errors": {
+        "badRequest": "This address is not valid.",
+        "notFound": "Page not found.",
+        "unauthenticated": "Sign in to continue.",
+        "forbidden": "You do not have access to this page.",
+        "unavailable": "The service is temporarily unavailable. Please try again."
+      }
+    }
+  }
+}

package/dist/source/naeil-locale/messages/ja.json

@@ -0,0 +1,78 @@
+{
+  "naeil": {
+    "header": {
+      "nav": {
+        "home": "ホーム",
+        "projects": "プロジェクト",
+        "blog": "ブログ",
+        "navigation": "メインナビゲーション",
+        "menu": "メニュー",
+        "closeMenu": "メニューを閉じる"
+      },
+      "theme": {
+        "switchToLight": "ライトテーマに切り替える",
+        "switchToDark": "ダークテーマに切り替える"
+      },
+      "locale": {
+        "switchLabel": "言語"
+      },
+      "projects": {
+        "cc": {
+          "name": "Content Collector",
+          "description": "RSS、YouTube、Redditの自動収集 + AI要約"
+        },
+        "pkm": {
+          "name": "PKM",
+          "description": "個人ナレッジ管理 — ドキュメント解析、埋め込み、セマンティック検索"
+        },
+        "naeilUi": {
+          "name": "naeil-ui",
+          "description": "ミニマルデザインシステム — OKLCHトークン、Tailwind v4、shadcn"
+        },
+        "sa": {
+          "name": "Sustainability Analyzer",
+          "description": "ESGレポートAI分析 — PDF解析、定性評価、比較表の自動生成"
+        },
+        "babyAgent": {
+          "name": "Baby Agent",
+          "description": "育児AIエージェント — LINE Q&A、記録、リマインダー"
+        },
+        "status": {
+          "active": "アクティブ",
+          "coming": "準備中"
+        }
+      }
+    },
+    "account": {
+      "menu": "アカウントメニュー",
+      "account": "アカウント",
+      "login": "ログイン",
+      "logout": "ログアウト",
+      "busy": "ログアウト中…"
+    },
+    "footer": {
+      "navigation": "ナビゲーション",
+      "projects": "プロジェクト",
+      "blog": "ブログ",
+      "social": "ソーシャル",
+      "description": "Tomorrow starts here."
+    },
+    "locale": {
+      "names": {
+        "en": "English",
+        "ko": "한국어",
+        "ja": "日本語"
+      },
+      "pending": "言語を変更しています…",
+      "failed": "言語を変更できませんでした。作業内容は保持されています。",
+      "retry": "再試行",
+      "errors": {
+        "badRequest": "このアドレスは無効です。",
+        "notFound": "ページが見つかりません。",
+        "unauthenticated": "続けるにはログインしてください。",
+        "forbidden": "このページへのアクセス権限がありません。",
+        "unavailable": "サービスを一時的に利用できません。もう一度お試しください。"
+      }
+    }
+  }
+}

package/dist/source/naeil-locale/messages/ko.json

@@ -0,0 +1,78 @@
+{
+  "naeil": {
+    "header": {
+      "nav": {
+        "home": "홈",
+        "projects": "프로젝트",
+        "blog": "블로그",
+        "navigation": "주요 메뉴",
+        "menu": "메뉴",
+        "closeMenu": "메뉴 닫기"
+      },
+      "theme": {
+        "switchToLight": "밝은 테마로 전환",
+        "switchToDark": "어두운 테마로 전환"
+      },
+      "locale": {
+        "switchLabel": "언어"
+      },
+      "projects": {
+        "cc": {
+          "name": "Content Collector",
+          "description": "RSS, YouTube, Reddit 자동 수집 + AI 요약"
+        },
+        "pkm": {
+          "name": "PKM",
+          "description": "개인 지식 관리 — 문서 파싱, 임베딩, 시맨틱 검색"
+        },
+        "naeilUi": {
+          "name": "naeil-ui",
+          "description": "미니멀 디자인 시스템 — OKLCH 토큰, Tailwind v4, shadcn"
+        },
+        "sa": {
+          "name": "Sustainability Analyzer",
+          "description": "ESG 리포트 AI 분석 — PDF 파싱, 정성평가, 비교표 자동 생성"
+        },
+        "babyAgent": {
+          "name": "Baby Agent",
+          "description": "육아 AI 에이전트 — LINE 기반 Q&A, 기록, 리마인더"
+        },
+        "status": {
+          "active": "활성",
+          "coming": "준비 중"
+        }
+      }
+    },
+    "account": {
+      "menu": "계정 메뉴",
+      "account": "계정",
+      "login": "로그인",
+      "logout": "로그아웃",
+      "busy": "로그아웃 중…"
+    },
+    "footer": {
+      "navigation": "네비게이션",
+      "projects": "프로젝트",
+      "blog": "블로그",
+      "social": "소셜",
+      "description": "Tomorrow starts here."
+    },
+    "locale": {
+      "names": {
+        "en": "English",
+        "ko": "한국어",
+        "ja": "日本語"
+      },
+      "pending": "언어를 변경하는 중…",
+      "failed": "언어를 변경하지 못했습니다. 작업 내용은 유지됩니다.",
+      "retry": "다시 시도",
+      "errors": {
+        "badRequest": "올바르지 않은 주소입니다.",
+        "notFound": "페이지를 찾을 수 없습니다.",
+        "unauthenticated": "계속하려면 로그인하세요.",
+        "forbidden": "이 페이지에 접근할 권한이 없습니다.",
+        "unavailable": "일시적으로 서비스를 이용할 수 없습니다. 다시 시도하세요."
+      }
+    }
+  }
+}

package/docs/components/naeil-locale.md

@@ -0,0 +1,52 @@
+# Owned-service language runtime
+
+The opt-in `@naeil/ui/naeil-locale` entries support the registered naeil Next applications. English uses `/`, Korean `/ko`, and Japanese `/ja`, including deep routes. The URL determines the language. Cookie and browser preferences never redirect or overwrite it. The existing public `i18n/routing`, `Nav` and `Footer` APIs retain their previous behavior.
+
+Use exact `next-intl@4.14.8` with the shared server/client entries. Next and React remain external peers. Standalone header/footer imports do not require Next or next-intl.
+
+## Entries and ownership
+
+| Import | Responsibility |
+| --- | --- |
+| `@naeil/ui/naeil-locale` | Supported locales, strict service/route registry, `localePath`, `localeHref`, legacy receiving aliases and logical-route comparison |
+| `/naeil-locale/server` | `createNaeilLocaleProxy`, `createNaeilRequestConfig`, request access markers and `localeMetadata` |
+| `/naeil-locale/client` | Root `NaeilLocaleController`, locale `NaeilLocaleProvider`, `useLocaleController`, `useLocaleBeforeUnload` |
+| `/naeil-locale/messages` | Selected common/application JSON loading and namespace merge |
+| `/naeil-locale/checker` | Three-language key, nonempty value, ICU syntax and argument compatibility checks |
+| `/naeil-locale/chrome` | Existing header/account/footer presentation using the provider's selected common dictionary |
+
+Place the controller and app-owned session/business store in `app/layout.tsx`, above `[locale]`. Place the shared provider in `app/[locale]/layout.tsx` using the validated locale and server-loaded messages. Keep raw input, dialogs, undo, save/run controllers, stream readers and document-departure guards in the root lifetime. Locale remounts must not save, abort, reset, or seed a retained draft from older server props. Translate message keys at the rendering boundary, not inside persistent business state.
+
+The shared config sets `localePrefix: "as-needed"`, `localeDetection: false`, `localeCookie: false`, and `alternateLinks: false`. Consumers set Next's `skipProxyUrlNormalize: true` and `skipTrailingSlashRedirect: true`; normalization follows the existing protocol/auth checks. A trusted ingress consumer may pass `requestOrigin: request => existingValidatedRequestUrl(request).origin` to the proxy. This keeps alias redirects and internal rewrites on the validated authority, including local127.0.0.1 deployments. Never derive it from an unvalidated forwarded host.
+
+```tsx
+// app/layout.tsx — inside the existing html/body
+<NaeilLocaleController service="estimate" preferenceWritesEnabled={false}>
+  <BusinessStateProvider>{children}</BusinessStateProvider>
+</NaeilLocaleController>
+
+// app/[locale]/layout.tsx — validate locale and setRequestLocale on the server
+<NaeilLocaleProvider locale={locale} messages={await getMessages()}>
+  {children}
+</NaeilLocaleProvider>
+```
+
+Use `createNaeilRequestConfig({namespace: "estimate", messages: {en: () => import("../../messages/en.json"), ko: () => import("../../messages/ko.json"), ja: () => import("../../messages/ja.json")}})` in the next-intl request config. Every app JSON has exactly its own namespace. The package owns `naeil`; do not copy it into an app. The shared checker is a required build gate. The loader imports only the selected app dictionary and shared dictionary; an observable English recovery handles unexpected runtime omissions. Such omissions still fail acceptance.
+
+Render complete paths with `localePath` for same-service navigation and `localeHref` for owned service links. Pass those paths to base Next Link/router or anchors without another locale option. The controller performs `router.replace(href, {scroll: false})`, serializes requests and waits for the matching provider arrival. It restores a stable `data-naeil-focus-id`, input `name`, or `id`. Only a successful explicit selection may write preference; history, prefetch and direct visits do not. Storage failure cannot block a path change.
+
+The canonical chrome can be imported from `/naeil-locale/chrome` under the shared provider. Existing `/naeil-header` and `/naeil-footer` remain standalone compatibility adapters and include the small three-language common dictionary. Consumer Link, auth, save guards, frame overrides, desktop/mobile account locks and project data remain consumer-owned.
+
+## AB Storm registration (0.11.0 candidate)
+
+`service="abstorm"` binds to exactly `https://abstorm.naeil.dev`. Its protected UI inventory is `/`, `/new`, `/runs/[id]`, `/runs/[id]/report` and `/experts`; `/new?copy=<id>` uses the same registered page. All support English, Korean and Japanese paths. `/auth/session`, `/auth/logout`, `/api/*` and `/health` remain unlocalized protocol endpoints, with no UI exceptions. Unknown UI paths are rejected instead of inheriting the app’s catch-all history fallback.
+
+The inventory was checked against AB Storm source `087e67239db26506a73c51fde7a6d246e4a0d0d9`. Generic error documents use its existing `abstorm` title and no favicon. This registration does not add a default header/footer destination or application translations. Consumer provider, routing, authentication, message loading and upgrade remain app-owned; package registration alone does not establish production adoption.
+
+## Security and rollout
+
+The proxy runs exact existing protocol boundaries first, strips external private markers, strictly classifies UI paths, applies the existing app authorizer, and then runs next-intl. Protected entries without an authorizer fail closed. A marker is only a rendering hint: every protected server data read must independently authorize. RSC denial renders a valid localized access boundary and retains the root draft; it must not send login HTML or redirect an in-progress editor to another document. Keep the root beforeunload guard active during RSC failure and access recovery.
+
+`localePath` is not an auth-return validator. Keep existing exact return/invite/callback/relay origin and envelope validation. Protocol paths stay outside `[locale]`; localized protocol aliases are rejected. Public metadata advertises only available translations. Protected/auth/error UI is noindex without SEO alternates.
+
+Receiver deployment and sending are separate gates. `preferenceWritesEnabled` defaults to false. Before first exposure, validate a separate receiver-compatible fallback or the previous build's safe rejection of new paths. After all required receiver and auth receipts pass, enable the reviewed cross-service links and explicit preference writes. Keep package, source, hosted Docs, app identities, activation times and rollback receipts separate. Home and Baby are outside this migration.

package/docs/package-release.md

@@ -1,12 +1,16 @@
 # Package verification and release policy
 
-**Published exact baseline: 0.8.0** (source/tag `3f708e27d05212af7f7a5be769f13f871e8d10c7`, archive SHA-256 `6feb5a8cd50265ace584a0855432683b4127119377e08235282eaebd27081084`, 139 files). Registry download matched that frozen archive on 2026-10-29; tags were `latest=0.7.2`, `next=0.8.0`. Its Home menu/brand/status/controlled-sheet APIs and package-owned chrome typography are published. **0.9.0 is an unpublished candidate** for the adopted page-root frame rule. Contract version remains `1` only if all invariants pass. Historical releases/archives remain immutable; hosted Docs and service activation require separate receipts.
+**Published exact baseline: 0.10.0 — 2026-11-04.** Source/tag `455f2f9aedb108606af2f429c18281260eafd2dd`, frozen archive SHA-256 `a4a1e312f2f608358a10f9019c248af37a8172bb116d3bc506144442cb963fb4`, 175 regular files. Registry bytes matched; verified tags were `latest=0.7.2`, `next=0.10.0`. See the [publication and three-service acceptance receipts](https://github.com/naeil-dev/naeil-ui/blob/main/docs/design/shared-language-2026-11-04/implementation-progress.md). Historical releases, archives and receipts remain immutable; hosted Docs require their own receipt. The retained [local runner](https://github.com/naeil-dev/naeil-ui/blob/main/docs/rollout/local-runner.md) is a **0.7.x-only, contract 1** release/recovery tool, outside the current 0.10.0 deployment and recovery procedure. UI v2 names a design generation, not an npm major. Version-scoped installation is in the [README](../README.md#use-the-ui).
+
+## 0.11.0 candidate — AB Storm locale registry
+
+This additive API candidate registers AB Storm's five protected UI routes and error-document identity. Use the manual exact-archive procedure below, publish to `next` and preserve `latest`; the intended tag is `v0.11.0` at the frozen source. The historical 0.7.x runner transaction and chrome contract 1 remain unchanged. Package version, generated `/release` metadata and clean consumer fixture versions move together. Freeze only after all bundled documentation edits, and record source, digest, inventory and final checks outside the archive. Publication, registry verification, consumer adoption, GitHub Release and hosted Docs remain separate maintainer steps.
 
 ## Architecture
 
 One repository contains the shared package and the separate Next.js brand/example website. `@naeil/ui/ui` provides React primitives and generic Navigation/SiteFooter. The opt-in React-only `@naeil/ui/naeil-header` provides the complete actual naeil.dev branded header and `NaeilHeaderAccountControl`; see [its consumer contract](components/naeil-header.md). Owned apps render that control in `authSlot` and supply session state, pending state and guarded callbacks above the header. The legacy root is a framework compatibility entry with static Next/next-intl imports, even when selecting only Logo or a heading; React-only consumers use the documented shared deep modules. Next and next-intl are optional peers, not optional behavior inside the root. Supply them when importing that entry, Nav, Footer, or i18n/routing. Theme controls and Toaster use the framework-independent React library next-themes, retained as a runtime dependency.
 
-Owned services use `@naeil/ui/naeil-footer` for the canonical localized destinations in full/compact variants; generic SiteFooter and legacy Footer retain their APIs. Footer navigation adapters preserve application save/flush decisions and modified-click behavior. `@naeil/ui/release` is server-safe metadata; it contains no application artifact, credential or environment. Applications compile their own allowlisted artifact/source identity. See [the footer contract](components/naeil-footer.md). Current coordinator policy, selected services, activation and recovery evidence are maintained in the [rollout records](https://github.com/naeil-dev/naeil-ui/tree/main/docs/rollout); historical disabled-policy statements describe their dated checkpoints. Publishing a package, creating an update PR or merging it never establishes complete consumer rollout. Home Console is outside the selected shared-UI rollout.
+Owned services use `@naeil/ui/naeil-footer` for the canonical localized destinations in full/compact variants; generic SiteFooter and legacy Footer retain their APIs. Footer navigation adapters preserve application save/flush decisions and modified-click behavior. `@naeil/ui/release` is server-safe metadata; it contains no application artifact, credential or environment. Applications compile their own allowlisted artifact/source identity. See [the footer contract](components/naeil-footer.md). Historical 0.7.x release plans and transaction recovery use the [local rollout runner](https://github.com/naeil-dev/naeil-ui/blob/main/docs/rollout/local-runner.md); the [rollout records](https://github.com/naeil-dev/naeil-ui/tree/main/docs/rollout) preserve dated evidence and historical policies. Publishing a package, creating an update PR or merging it never establishes complete consumer rollout. Home Console is outside the selected shared-UI rollout.
 
 Website tools remain development dependencies so maintainers can develop both products. npm tarball consumers install only component runtime dependencies and their host React/ReactDOM. Build entries, package exports and packed checks constrain the public boundary. There is no bundled website action, Supabase helper, Three/hero/cursor module, blog engine or full application message catalog. The opt-in header includes only its three header dictionaries and canonical project catalog. Its 0.7.2 default catalog contains naeil-ui and references the official `https://naeil.dev/images/whale.png` URL and require network access; no image bytes are bundled, and unresolved artwork redistribution provenance remains in [third-party notices](../THIRD_PARTY_NOTICES.md).
 
@@ -31,6 +35,17 @@ pnpm exec playwright install chromium firefox webkit
 pnpm test:browser
 ```
 
+The chrome fixture server and standalone navigation sample use `NAEIL_UI_FIXTURE_PORT`, with the unchanged default defined in `scripts/chrome-fixture-config.ts` in the repository. The same module supplies every fixture URL. An explicit port also isolates generated fixtures, test results and HTML reports by port; leave it unset to retain the existing CI paths. Choose a free integer port from 1 to 65535.
+
+For two concurrent fixture-only runs in one worktree, use separate terminals:
+
+```sh
+NAEIL_UI_CHROME_ONLY=1 NAEIL_UI_FIXTURE_PORT=16081 pnpm test:browser e2e/page-frame.spec.ts --project=chromium
+NAEIL_UI_CHROME_ONLY=1 NAEIL_UI_FIXTURE_PORT=16082 pnpm test:browser e2e/page-frame.spec.ts --project=chromium
+```
+
+`NAEIL_UI_CHROME_ONLY=1` skips the unrelated Storybook server. Full suites still use `NAEIL_UI_STORYBOOK_PORT` for Storybook. Do not overlap an unset-port run (which cleans the default `test-results` directory) with custom-port runs in the same worktree. The standalone sample uses the same port setting: `NAEIL_UI_FIXTURE_PORT=16083 pnpm exec tsx scripts/serve-navigation-sample.ts`. Stop standalone previews after use; Playwright stops its own fixture server.
+
 `check:package:boundary` inspects an actual `npm pack --ignore-scripts` archive for every declared export, runtime dependencies, source aliases, relative imports, required CSS/tokens/documents/notices and forbidden website payload. `check:consumers` separately installs that tarball with npm into two temporary directories. It builds the reusable React example with Vite/Tailwind, type-checks with library checks enabled, imports shared deep modules, checks SSR and CSS, and asserts Next/Supabase/Three are absent. A separate Next production build exercises root exports and the deep paths observed in the reachable Next consumer, with consumer-owned messages and no auth backend. Neither fixture uses repository dependency symlinks. Network access is needed for uncached npm dependencies; temporary installs are removed on completion or failure.
 
 For a frozen release candidate, both archive-producing checks can enforce the reviewed SHA-256 before extraction or consumer installation:
@@ -50,6 +65,14 @@ The explicit font-notice regression gate copies the real React fixture config in
 
 ## Publication and deployment
 
+### Verified 0.10.0 publication and service acceptance — 2026-11-04
+
+The [registry receipt](https://github.com/naeil-dev/naeil-ui/releases/download/v0.10.0/npm-registry-verification.json) verifies the exact frozen archive listed above, including all 175 regular members. [Release v0.10.0](https://github.com/naeil-dev/naeil-ui/releases/tag/v0.10.0) retains its assets at the frozen source. [Implementation progress](https://github.com/naeil-dev/naeil-ui/blob/main/docs/design/shared-language-2026-11-04/implementation-progress.md) and [acceptance](https://github.com/naeil-dev/naeil-ui/blob/main/docs/design/shared-language-2026-11-04/acceptance.md) record Site, Jev and Estimate separately. Those service identities and recovery procedures are outside the old 0.7.x runner; its preserved approval and transaction must not be reused for this release.
+
+### Historical 0.8.0 registry checkpoint — 2026-10-29
+
+The published 0.8.0 archive matched frozen SHA-256 `6feb5a8cd50265ace584a0855432683b4127119377e08235282eaebd27081084` (139 files, source/tag `3f708e27d05212af7f7a5be769f13f871e8d10c7`). Registry tags at that dated checkpoint were `latest=0.7.2`, `next=0.8.0`. Its Home menu/brand/status/controlled-sheet APIs and package-owned chrome typography remain part of the current public API. This receipt remains historical and does not establish the current registry tags or hosted Docs source.
+
 ### Verified 0.7.1 registry publication and maintained Docs — 2026-10-23
 
 The published release preserves these immutable identities:
@@ -66,7 +89,7 @@ The frozen archive was published directly with scripts disabled. npm records pub
 
 The archive's bundled guides are an immutable preparation snapshot, including 0.6.0 installation copy. Release notes must point to maintained instructions. Deploy Docs from a separately reviewed commit containing current guidance, the `v0.7.1` link correction and the corrected manual workflow. Record that Docs SHA, workflow run, deployment and actual hosted checks separately; retain `v0.7.1` at the frozen package source.
 
-Postpublication registry checks passed on 2026-10-23. Separate fresh React/Next fixtures installed exact `@naeil/ui@0.7.1` from npmjs with independent empty caches and no repository dependency symlinks; every installed file matched the frozen 139-file inventory in both fixtures. Types, production builds, public root/deep import boundaries, release/footer/account SSR and browser checks passed, including the React fixture's absence of Next/Supabase/Three. The retained `registry-receipt.json` and successful `npm-publication-verification.json` bind these checks to the frozen source/archive; the latter records `checkedAt: 2026-10-23T01:19:50.385Z`. At the 01:19 UTC registry checkpoint, the tag had been pushed and the Release draft prepared. GitHub Release publication, hosted Docs and standing activation require separate receipts; see the release assets and [current rollout runbook](https://github.com/naeil-dev/naeil-ui/blob/main/docs/rollout/standing-rollout.md). Native/manual, real OAuth and global service-discovery evidence retain their separate scopes and limits.
+Postpublication registry checks passed on 2026-10-23. Separate fresh React/Next fixtures installed exact `@naeil/ui@0.7.1` from npmjs with independent empty caches and no repository dependency symlinks; every installed file matched the frozen 139-file inventory in both fixtures. Types, production builds, public root/deep import boundaries, release/footer/account SSR and browser checks passed, including the React fixture's absence of Next/Supabase/Three. The retained `registry-receipt.json` and successful `npm-publication-verification.json` bind these checks to the frozen source/archive; the latter records `checkedAt: 2026-10-23T01:19:50.385Z`. At the 01:19 UTC registry checkpoint, the tag had been pushed and the Release draft prepared. GitHub Release publication, hosted Docs and service rollout require separate receipts; see the release assets and [historical 0.7.x rollout runbook](https://github.com/naeil-dev/naeil-ui/blob/main/docs/rollout/local-runner.md). Native/manual, real OAuth and global service-discovery evidence retain their separate scopes and limits.
 
 ### 0.6.0 release scope — 2026-10-16
 
@@ -104,7 +127,7 @@ The immutable npm archive's bundled guides are the release-preparation snapshot.
 
 ### Release procedure
 
-Maintained Storybook resolves relative Markdown guide links against the published `v0.7.2` source `40a3928e24cd2f0141be3e605eed0a75260938fd`. The published 0.8.0 archive and 0.9.0 candidate keep that published guide-link target until a separately reviewed Docs release. That tag is independent of the reviewed Docs deployment SHA. Hosted verification checks that the pinned links resolve; the unpublished `v0.7.0` tag is not a valid target. Historical foundation/source-authority links remain at their original revisions. Freeze subsequent documentation changes separately from immutable release archives.
+Maintained Storybook resolves relative Markdown guide links against the published `v0.7.2` source `40a3928e24cd2f0141be3e605eed0a75260938fd`. Package releases keep that published guide-link target until a separately reviewed Docs release. That tag is independent of the reviewed Docs deployment SHA. Hosted verification checks that the pinned links resolve; the unpublished `v0.7.0` tag is not a valid target. Historical foundation/source-authority links remain at their original revisions. Freeze subsequent documentation changes separately from immutable release archives.
 
 The authorized 0.3.0 release completed main merge, npm 0.3.0, a GitHub Release and hosted Docs as recorded above. The release maintainer performs external authentication and publication; documentation preparation does not itself execute those operations. The automatic verification workflow does not publish or deploy. Record native/manual observations with their actual scope and carry unrun checks as limitations; do not substitute automated WebKit/axe checks or publication authorization for human certification.
 
@@ -121,9 +144,11 @@ npm publication, GitHub Releases, main merge and hosted Docs are distinct operat
 `vercel.json` disables Git deployments only for `feat/public-ui-readiness`. Other branches retain Vercel's default behavior, so merging or pushing another branch requires a separate deployment decision. The automatic GitHub Actions checks are verification-only; enabling repository workflows is not evidence of a hosted site or approved release.
 
 
-### Manual exact-archive preparation for 0.9.0 (following 0.8.0)
+### Historical manual exact-archive preparation for 0.9.0 (following 0.8.0)
+
+The following preparation requirements and deployment hold describe the October 29 checkpoint. The November 4 release and accepted service state are recorded above; this historical section does not describe current service versions or pending approval.
 
-The standing `scripts/rollout/prepare-release.mjs` accepts consecutive stable 0.7.x releases only. Do not change rollout policy, `release.json` or the chrome contract to admit 0.9.0. Use the manual release procedure above: complete G1–G7 from the [adopted root-frame contract](https://github.com/naeil-dev/naeil-ui/blob/434b7d07235316097ca3a55265ee02c1422b0cfd/docs/superpowers/specs/2026-10-29-page-root-scrollbar-gutter.md), including the retained 0.8.0 P1–P5 regressions, freeze the exact source SHA/archive, then run boundary and clean React/Next checks with `NAEIL_UI_EXPECTED_ARCHIVE_SHA256`. The paired browser gate accepts `NAEIL_UI_CHROME_PACKAGE=/absolute/extracted/package` to exercise that exact archive, alongside SHA-512-pinned 0.7.2 and SHA-256-pinned frozen 0.8.0. Reference-only root/lock CSS adjustments are separate hashed fixture files; immutable archives stay untouched. Both classic and overlay jobs require actual probes. Viewport captures have geometry guards; all acceptance measurement precedes any terminal fullPage capture. It retains numeric differences and screenshots for human review; new renders never replace expectations automatically.
+The retained `scripts/rollout/prepare-release.mjs` accepts consecutive stable 0.7.x releases only. Do not change rollout policy, `release.json` or the chrome contract to admit 0.9.0. Use the manual release procedure above: complete G1–G7 from the [adopted root-frame contract](https://github.com/naeil-dev/naeil-ui/blob/434b7d07235316097ca3a55265ee02c1422b0cfd/docs/superpowers/specs/2026-10-29-page-root-scrollbar-gutter.md), including the retained 0.8.0 P1–P5 regressions, freeze the exact source SHA/archive, then run boundary and clean React/Next checks with `NAEIL_UI_EXPECTED_ARCHIVE_SHA256`. The paired browser gate accepts `NAEIL_UI_CHROME_PACKAGE=/absolute/extracted/package` to exercise that exact archive, alongside SHA-512-pinned 0.7.2 and SHA-256-pinned frozen 0.8.0. Reference-only root/lock CSS adjustments are separate hashed fixture files; immutable archives stay untouched. Both classic and overlay jobs require actual probes. Viewport captures have geometry guards; all acceptance measurement precedes any terminal fullPage capture. It retains numeric differences and screenshots for human review; new renders never replace expectations automatically.
 
 Before npm publication, the separately approved source push must make the linked adopted contract at `434b7d07235316097ca3a55265ee02c1422b0cfd` public. Immediately after that push, verify an anonymous HTTP 200 for the exact guide URL and confirm its status says **rev 1, adopted 2026-10-29**. Local link/boundary checks do not establish public reachability. Source push may trigger Vercel deployment and retains its own approval boundary.