banhaten 0.3.0 → 0.5.0

package/docs/design-system/template-gap-audit.md

@@ -0,0 +1,32 @@
+# Template Gap Audit
+
+Last updated: 2026-08-23
+
+This audit records repeated friction encountered while composing the 60-template catalog. It does not automatically promote every local composition into a component. Candidates should pass the roadmap's reuse, accessibility, direction, and API-stability gates.
+
+## Prioritized findings
+
+| Priority | Missing capability | Evidence from the catalog | Current workaround | Recommended ownership |
+| --- | --- | --- | --- | --- |
+| P1 | Responsive app-shell and layout primitives | Nearly every dashboard, settings, data, and operations page needed the same container, split-pane, metric-grid, and responsive collapse rules | Local CSS grids using spacing and surface tokens | Add documented `Container`, `Stack`, `Cluster`, `Grid`, and `AppShell` layout patterns plus breakpoint/container tokens |
+| P1 | Stat / KPI card pattern | Executive, product, sales, commerce, finance, campaign, and widget designs repeat label/value/change anatomy | Local Card composition with Badge and trend icon | Promote a `StatCard` pattern with value, comparison, intent, sparkline slot, loading state, and RTL-safe trend semantics |
+| P1 | Key-value and summary rows | Checkout, billing, profile, resource detail, transfers, and review flows need dense label/value groupings | Card, Attribute, Divider, and bespoke rows | Add a responsive `DescriptionList` / `SummaryList` pattern with actions, status, truncation, and stacked mode |
+| P1 | Data-visualization recipes | Dashboards and finance screens repeatedly need sparklines, time series, funnels, comparison bars, legends, and no-data states | Raw Recharts composition inside ChartContainer | Publish chart recipes and defaults for sparkline, KPI trend, time series, bar comparison, funnel, legend, tooltip, empty, and loading states |
+| P1 | Amount and currency field | Send money, FX quote, wallets, savings, billing, and checkout all need amount, currency, decimal, and locale behavior | Generic Input plus nearby Badge/Button | Add an `AmountInput` pattern with currency selector, precision rules, localized formatting, min/max, fees, and RTL QA |
+| P2 | Structured commerce form recipes | Checkout and billing need address, card, delivery, tax, and order-summary structures | Generic Input, Checkbox, Card, and Divider composition | Document `AddressForm`, `PaymentMethod`, and `OrderSummary` patterns before considering dedicated components |
+| P2 | Schedule and board patterns | Schedule planner, editorial calendar, hiring pipeline, project board, and room planner could only approximate their core layouts | Cards and lists arranged in local grids | Add accessible calendar/schedule and board patterns with keyboard navigation, overflow, selection, drag alternatives, and mobile behavior |
+| P2 | Rich text and message composer | Shared inbox, conversation, email campaign, and content workflows need recipients, formatting, attachments, variables, and send state | Textarea, Toolbar, Tag, File Upload, and Button assembled locally | Define a `Composer` pattern with slots for recipients, toolbar, variable chips, attachments, drafts, validation, and send status |
+| P2 | Media and asset browser | Product detail and content library need aspect-ratio thumbnails, selection, metadata, upload progress, and preview | Card, Aspect Ratio, File Upload, and generic image assets | Add `MediaCard`, selectable asset grid, and preview-detail patterns; keep storage and transformation product-owned |
+| P2 | Status and health summary | Infrastructure, incidents, shipment, integrations, and widgets repeat status icon, message, metric, and history anatomy | Badge, Alert, Progress, and local icon wrappers | Add `StatusSummary` and `ServiceHealthRow` patterns with severity, timestamp, trend, actions, and accessible non-color cues |
+| P3 | Map and spatial slot guidance | Shipment tracking and room planning cannot express a real map or floor plan with current components | List/detail summaries only | Document a neutral map/canvas host contract and overlay controls; keep the mapping engine and spatial assets outside the design system |
+| P3 | Product illustration and empty-state asset guidance | Authentication, onboarding, commerce, and zero-data moments need richer owned visuals | One existing abstract image plus icon-led Empty State | Define approved illustration ratios, theming, cropping, alt-text, and loading rules; maintain real assets separately from component code |
+
+## What is not missing
+
+Table, File Upload, Empty State, ChartContainer, Page Header, Steps, Sidebar, Modal, Tabs, Toolbar, and the core form controls already provide useful foundations. The friction above is primarily at the composition, recipe, and responsive-layout layers; duplicating those existing primitives would make the system harder to maintain.
+
+## Suggested sequence
+
+1. Stabilize layout primitives, StatCard, SummaryList, chart recipes, and AmountInput because they recur across the largest number of templates.
+2. Validate commerce forms, schedules/boards, Composer, media browser, and status summaries in two real product flows each.
+3. Keep map engines and illustration assets as integration guidance unless repeated product usage reveals a stable design-system API.

package/docs/design-system/templates.md

@@ -0,0 +1,59 @@
+# Templates
+
+Templates are Banhaten's composition tier: reusable page, flow, and widget starting points assembled from the existing token and component contracts. They sit above Components and Patterns, and below product-specific implementation.
+
+The live catalog is available at `#templates` in the playground. It uses a text-first, single-column directory so full application screens are not compressed into competing thumbnails. Search, category, and type filters lead to a dedicated hash route for each template, where one design is shown at full content width with previous/next navigation, composition notes, and starter-code copying. Templates are examples rather than stable registry packages; product data, routing, validation, and domain behavior remain application-owned.
+
+## Tier boundaries
+
+| Tier | Purpose | Examples |
+| --- | --- | --- |
+| Tokens | Visual decisions and modes | Color, type, spacing, radius, elevation |
+| Components | Reusable interaction primitives | Button, Input, Table, Modal, Chart |
+| Patterns | Repeated task-level combinations | Page Header, File Upload, Empty State, Steps |
+| Templates | Page, flow, and widget starting points | Checkout, analytics dashboard, exchange-rate widget |
+| Lab | Screenshot-driven visual and quality experiments | Background tests and comparison workspaces |
+
+Templates do not introduce a second visual language. Every surface, border, state, radius, type style, spacing decision, and shadow resolves through Banhaten's semantic tokens or an existing component contract.
+
+## Research basis
+
+The catalog uses the breadth and taxonomy of established libraries as research inputs, without copying their styling or exact layouts:
+
+- [shadcn/ui Blocks](https://ui.shadcn.com/blocks) separates larger dashboard, authentication, and sidebar compositions from individual components.
+- [Tailwind Plus Application UI](https://tailwindcss.com/plus/ui-blocks/application-ui), [Ecommerce](https://tailwindcss.com/plus/ui-blocks/ecommerce), and marketing collections cover task-specific sections and screens.
+- [Material UI Templates](https://mui.com/material-ui/getting-started/templates/) includes sign-in, checkout, CRUD, dashboard, and marketing starting points.
+- [Carbon Patterns](https://carbondesignsystem.com/patterns/overview/) defines patterns as reusable combinations that help users complete goals and flows.
+- [Shopify App Home patterns](https://shopify.dev/docs/api/app-home/patterns) distinguishes full-page templates from smaller compositions.
+- [Ant Design](https://ant.design/docs/spec/overview/) demonstrates both base components and business-oriented examples.
+
+## Catalog inventory
+
+| Category | Type | Included templates |
+| --- | --- | --- |
+| Authentication | Flow | Centered sign in, Split sign in, Create account, Invite acceptance, Password recovery, Two-step verification |
+| Dashboards | Page | Executive overview, Product analytics, Sales pulse, Support operations, Infrastructure health, Team workload |
+| Finance | Flow | Wallet overview, Send money, Foreign exchange quote, Crypto portfolio, Card controls, Savings plan |
+| Commerce | Page | Storefront overview, Product detail, Catalog manager, Cart summary, Checkout flow, Order tracking |
+| Data | Page | Resource index, Resource detail, Data source browser, Import mapping, Audit log, Approval queue |
+| Collaboration | Page | Team directory, Activity center, Shared inbox, Conversation detail, Project board, Meeting agenda |
+| Operations | Page | Shipment tracking, Schedule planner, Incident response, Hiring pipeline, Benefits enrollment, Room planner |
+| Settings & Admin | Page | Profile settings, Security settings, Billing settings, Notification preferences, Workspace members, Integrations hub |
+| Marketing & Content | Page | Campaign overview, Email composer, Editorial calendar, Content library, Launch checklist, Customer story |
+| Widgets | Widget | Metric comparison, Conversion funnel, Task progress, Exchange rate, Server status, Recent transactions |
+
+Total: 60 templates across 10 categories.
+
+## Quality contract
+
+- A template must remain legible in LTR and RTL and in light and dark modes.
+- The catalog must show template names and descriptions as a directory; full template canvases appear only on their dedicated pages.
+- Template chrome and previews use Banhaten tokens; raw colors, bespoke shadows, and copied external CSS are not allowed.
+- Inputs and other form controls inherit Banhaten's default `lg` density. Compact controls are reserved for genuinely constrained desktop tables and toolbars, never as a way to squeeze a template into its preview.
+- Product imagery must come from a real owned asset. Icons use the supported icon family.
+- Visible controls in the gallery's main journey work: search, filters, pagination, preview, close, mode selection, and copy.
+- Repeated composition friction is recorded in the [template gap audit](./template-gap-audit.md) before a new component or pattern is proposed.
+
+## Promotion path
+
+A template can become an installable `registry:block` only after it has a stable public composition API, realistic data and empty/loading/error states, accessibility and direction tests, documentation, and evidence of reuse in more than one product context. Until then, the catalog remains an exploration and adoption aid rather than generated source ownership.

package/docs/design-system/token-governance.md

@@ -1,60 +1,72 @@
-# Token Governance
-
-Banhaten components must be built from Banhaten tokens. Component source may use:
-
-- Generated `--bh-*` semantic tokens.
-- System, typography, effect, and component variables compiled from their owned
-  fragments under `tokens/source/` into the published `cssVariables` contract.
-- shadcn alias bridge variables such as `--background`, `--foreground`, and `--ring` only when they point back to Banhaten tokens.
-- Documented exception-ledger values when the value is external, brand-owned, or required by a third-party primitive API.
-
-Do not add raw component styling literals directly to `registry/components`:
-
-- Raw color literals.
-- Raw `px`, `rem`, or `ms` values outside approved media-query breakpoints.
-- Raw opacity utilities such as `opacity-0` or `opacity-100`.
-- Raw z-index, ring width, duration, icon size, or compact spacing utilities.
-- Component-local `color-mix()` percentages.
-- Legacy `--ds-*` fallbacks.
-
-`npm run tokens:check` enforces the generated CSS contract and component token usage.
-
-Structured tokens and aliases are authored in the domain and component-owned
-fragments under `tokens/source/`. `tokens/banhaten.tokens.json` is output-only
-and deterministically compiled from that manifest. Authored Tailwind mappings,
-keyframes, global and accessibility rules, and typography utilities live in
-`tokens/banhaten.utilities.css`. The distributable
-`registry/styles/globals.css` is regenerated from the compiled token catalog and
-that authored CSS source.
-
-The generator emits the complete default-theme graph once, then emits only declarations whose values differ for each alternate theme. Dark mode and alternate themes inherit unchanged scoped aliases through the cascade. This keeps the live graph auditable without duplicating identical declarations.
-
-The default appearance deliberately composes two concerns: `blue` owns brand
-roles and `gray` owns the neutral ramp. As a result, default product surfaces
-are achromatic, while links, focus states, and primary actions remain blue.
-`cssContract.defaultTheme` and `cssContract.defaultNeutralTheme` record that
-composition. `npm run tokens:build` synchronizes it into the authored default
-theme and semantic color-mode values before compiling the public artifacts.
-Alternate brand themes keep their reviewed neutral ramps unless their source is
-explicitly changed.
-
-Color values are design-owned. The generated Color Contrast page reports failing combinations and recommendations, but automation must not silently change source colors. A color change requires an explicit design review and regeneration of the contrast baseline.
-
-## Exception Ledger
-
-The following exceptions are allowed only in token generation or documented alias source, not directly in component implementation:
-
-| Exception | Reason | Owner |
-| --- | --- | --- |
-| Social provider marks | Apple, Facebook, Google, LinkedIn, Twitter, and WhatsApp colors and icon geometry must preserve provider identity; color must still flow through `currentColor` and Banhaten social variables. | Component alias source and social button source |
-| Payment or illustrative mark geometry | Some Figma-matched marks use fractional geometry that cannot be expressed cleanly through the global spacing scale. | Component alias source |
-| Effect and shadow stops | The supplied token zips do not include effect tokens, so component shadow aliases document those values. | Component alias source |
-| Media-query breakpoints | CSS custom properties are not reliable in media-query conditions. | Component CSS with local comment |
-| Radix numeric offsets | Some Radix APIs require JavaScript numbers instead of CSS variables; comments must pair each number with its matching token. | Component source |
-| Expanded composition widths | Larger app compositions may expose public layout aliases or documentation-only layout aliases. | Expanded component docs |
-
-If a new literal is needed, add it to an alias or the exception ledger before using it.
-
-## Public Override Surface
-
-Stable override points are CSS variables emitted in `registry/styles/globals.css`. Prefer overriding component aliases rather than editing installed component source. Product teams should use local wrapper components for behavior and keep Banhaten files generated-owned.
+# Token Governance
+
+Banhaten components must be built from Banhaten tokens. Component source may use:
+
+- Generated `--bh-*` semantic tokens.
+- System, typography, effect, and component variables compiled from their owned
+  fragments under `tokens/source/` into the published `cssVariables` contract.
+- shadcn alias bridge variables such as `--background`, `--foreground`, and `--ring` only when they point back to Banhaten tokens.
+- Documented exception-ledger values when the value is external, brand-owned, or required by a third-party primitive API.
+
+Do not add raw component styling literals directly to `registry/components`:
+
+- Raw color literals.
+- Raw `px`, `rem`, or `ms` values outside approved media-query breakpoints.
+- Raw opacity utilities such as `opacity-0` or `opacity-100`.
+- Raw z-index, ring width, duration, icon size, or compact spacing utilities.
+- Component-local `color-mix()` percentages.
+- Legacy `--ds-*` fallbacks.
+
+`npm run tokens:check` enforces the public token schema, generated CSS contract,
+and component token usage. `schema/tokens.schema.json#/$defs/cssVariableName`
+owns the naming rule for published variables and alias targets: `--bh-*` and
+`--elevation-*`. The compiler, CSS generator, component metadata scanner, and CSS
+reference checks share that contract through `scripts/token-schema.mjs`.
+Compilation and direct CSS generation validate the full catalog before comparing
+or writing artifacts, so schema failures stop both `tokens:check` and
+`contracts:check`.
+
+Structured tokens and aliases are authored in the domain and component-owned
+fragments under `tokens/source/`. `tokens/banhaten.tokens.json` is output-only
+and deterministically compiled from that manifest. Authored Tailwind mappings,
+keyframes, global and accessibility rules, and typography utilities live in
+`tokens/banhaten.utilities.css`. The distributable
+`registry/styles/globals.css` is regenerated from the compiled token catalog and
+that authored CSS source.
+
+Each theme boundary emits its complete palette, semantic aliases, effects, and
+dependent component aliases. Dark mode rebinds the semantic and component graph
+both on `.dark` elements and on themed descendants. CSS custom properties inherit
+computed values, so identical `var()` declarations must be repeated at these
+boundaries to resolve against the local theme. Other typography and layout tokens
+retain their existing inheritance behavior. The token contract check verifies
+these graphs for every supported light and dark theme scope.
+
+The default appearance uses `gray` for both brand roles and the neutral ramp.
+As a result, product surfaces, links, focus states, and primary actions are
+monochrome by default. `cssContract.defaultTheme` and
+`cssContract.defaultNeutralTheme` record that composition. `npm run
+tokens:build` synchronizes it into the authored default theme and semantic
+color-mode values before compiling the public artifacts. Alternate brand themes
+keep their reviewed neutral ramps unless their source is explicitly changed.
+
+Color values are design-owned. The generated Color Contrast page reports failing combinations and recommendations, but automation must not silently change source colors. A color change requires an explicit design review and regeneration of the contrast baseline.
+
+## Exception Ledger
+
+The following exceptions are allowed only in token generation or documented alias source, not directly in component implementation:
+
+| Exception | Reason | Owner |
+| --- | --- | --- |
+| Social provider marks | Apple, Facebook, Google, LinkedIn, Twitter, and WhatsApp colors and icon geometry must preserve provider identity; color must still flow through `currentColor` and Banhaten social variables. | Component alias source and social button source |
+| Payment or illustrative mark geometry | Some Figma-matched marks use fractional geometry that cannot be expressed cleanly through the global spacing scale. | Component alias source |
+| Effect and shadow stops | The supplied token zips do not include effect tokens, so component shadow aliases document those values. | Component alias source |
+| Media-query breakpoints | CSS custom properties are not reliable in media-query conditions. | Component CSS with local comment |
+| Radix numeric offsets | Some Radix APIs require JavaScript numbers instead of CSS variables; comments must pair each number with its matching token. | Component source |
+| Expanded composition widths | Larger app compositions may expose public layout aliases or documentation-only layout aliases. | Expanded component docs |
+
+If a new literal is needed, add it to an alias or the exception ledger before using it.
+
+## Public Override Surface
+
+Stable override points are CSS variables emitted in `registry/styles/globals.css`. Prefer overriding component aliases rather than editing installed component source. Product teams should use local wrapper components for behavior and keep Banhaten files generated-owned.

package/package.json

@@ -1,98 +1,98 @@
-{
-  "name": "banhaten",
-  "version": "0.3.0",
-  "description": "Banhaten design system: an Arabic and English-first React design system with shadcn-style component installation.",
-  "type": "module",
-  "bin": {
-    "banhaten": "src/cli/index.js"
-  },
-  "files": [
-    "src",
-    "registry/index.json",
-    "registry/component-contract.json",
-    "registry/components",
-    "registry/examples",
-    "registry/guidance",
-    "registry/hooks",
-    "registry/styles",
-    "registry/utils",
-    "registry/assets/activity-feed-avatar.png",
-    "registry/assets/avatars/avatar-01.jpg",
-    "registry/assets/images/art-01.jpg",
-    "registry.json",
-    "tokens/banhaten.tokens.json",
-    "schema",
-    "docs",
-    "banhaten.config.example.json",
-    "README.md",
-    "CHANGELOG.md",
-    "CONTRIBUTING.md",
-    "SECURITY.md",
-    "LICENSE"
-  ],
-  "scripts": {
-    "build": "npm --prefix playground ci --include=dev --include=optional && npm --prefix playground run build",
-    "build:railway": "npm --prefix playground ci --include=dev --include=optional && npm --prefix playground run build:railway",
-    "start": "node playground/scripts/serve-static.mjs playground/dist",
-    "check": "node --check src/cli/index.js && node --check src/cli/command-line.js && node --check src/cli/doctor.js && node --check src/cli/config-editors.js && node --check src/cli/source-scanner.js && node --check src/cli/jsonc.js && node --check src/cli/vite-config.js && node --check src/cli/install-plan.js && node --check src/cli/install-receipt.js && node --check src/cli/package-install-state.js && node --check src/cli/package-manager.js && node --check src/cli/package-plan.js && node --check src/cli/package-version.js && node --check scripts/compile-token-catalog.mjs && node --check scripts/sync-default-theme-neutral-values.mjs && node --check scripts/token-catalog-test.mjs && node --check scripts/registry-catalog.mjs && node --check scripts/generate-registry-index.mjs && node --check scripts/generate-shadcn-registry.mjs && node --check scripts/normalize-component-docs.mjs && node --check scripts/package-artifact.mjs && node --check scripts/check-package-contents.mjs && node --check scripts/select-react-compatibility.mjs && npm run contracts:check && npm run cli:test && npm run tokens:check && npm run components:ownership:check && npm run registry:check && npm run docs:check && npm run package:check && npm run playground:build && npm run playground:test:browser && npm run playground:audit",
-    "contracts:check": "node scripts/validate-contracts.mjs",
-    "cli:test": "node scripts/cli-argument-test.mjs && node scripts/cli-dependency-test.mjs && node scripts/cli-install-plan-test.mjs && node scripts/cli-integration-test.mjs && node scripts/cli-doctor-test.mjs",
-    "playground:build": "npm --prefix playground run build",
-    "playground:dev": "npm --prefix playground run dev",
-    "playground:test": "npm --prefix playground run test",
-    "playground:test:browser": "npm --prefix playground run test:browser",
-    "playground:audit": "npm --prefix playground audit --audit-level=high",
-    "package:check": "node scripts/generate-registry-index.mjs --check && node scripts/compile-token-catalog.mjs --check && node scripts/check-package-contents.mjs",
-    "registry:build": "node scripts/generate-registry-index.mjs --write",
-    "registry:check": "node scripts/generate-registry-index.mjs --check && node scripts/check-registry-mirrors.mjs && node scripts/generate-shadcn-registry.mjs --check && node scripts/registry-runtime-exports-test.mjs && node scripts/check-isolated-registry-installs.mjs --packed",
-    "registry:export": "node scripts/generate-registry-index.mjs --write && node scripts/generate-shadcn-registry.mjs --write",
-    "registry:exports": "node scripts/check-isolated-registry-installs.mjs --write-exports",
-    "registry:sync": "node scripts/check-registry-mirrors.mjs --write",
-    "components:tokens:check": "node scripts/check-component-token-usage.mjs",
-    "components:ownership:check": "npm --prefix playground run test:ownership",
-    "components:tokens:metadata": "node scripts/sync-component-token-metadata.mjs",
-    "docs:check": "node scripts/check-component-docs.mjs && node scripts/normalize-component-docs.mjs",
-    "docs:normalize": "node scripts/normalize-component-docs.mjs --write",
-    "smoke": "node src/cli/index.js list",
-    "tokens:aliases:check": "node scripts/sync-default-theme-neutral-values.mjs",
-    "tokens:aliases:sync": "node scripts/sync-default-theme-neutral-values.mjs --write",
-    "tokens:build": "npm run tokens:aliases:sync && node scripts/compile-token-catalog.mjs --write && node scripts/generate-token-css.mjs --write",
-    "tokens:check": "npm run tokens:aliases:check && node scripts/compile-token-catalog.mjs --check && node scripts/token-catalog-test.mjs && node scripts/generate-token-css.mjs --check && node scripts/check-token-css-reproducibility.mjs && node scripts/check-token-contract.mjs && npm run components:tokens:check && npm run components:tokens:metadata"
-  },
-  "engines": {
-    "node": ">=18.18"
-  },
-  "peerDependencies": {
-    "react": "^18.2.0 || ^19.0.0",
-    "react-dom": "^18.2.0 || ^19.0.0",
-    "tailwindcss": "^4.0.0"
-  },
-  "keywords": [
-    "banhaten",
-    "design-system",
-    "react",
-    "shadcn",
-    "rtl",
-    "arabic",
-    "components"
-  ],
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/AhmadGalal85/Banhaten-design-system.git"
-  },
-  "bugs": {
-    "url": "https://github.com/AhmadGalal85/Banhaten-design-system/issues"
-  },
-  "homepage": "https://github.com/AhmadGalal85/Banhaten-design-system/tree/main/docs",
-  "directories": {
-    "doc": "docs"
-  },
-  "author": "Ahmad Galal",
-  "dependencies": {
-    "ajv": "^8.20.0",
-    "minimatch": "^10.2.5",
-    "semver": "^7.8.5",
-    "yaml": "^2.9.0"
-  }
-}
+{
+  "name": "banhaten",
+  "version": "0.5.0",
+  "description": "Banhaten design system: an Arabic and English-first React design system with shadcn-style component installation.",
+  "type": "module",
+  "bin": {
+    "banhaten": "src/cli/index.js"
+  },
+  "files": [
+    "src",
+    "registry/index.json",
+    "registry/component-contract.json",
+    "registry/components",
+    "registry/examples",
+    "registry/guidance",
+    "registry/hooks",
+    "registry/styles",
+    "registry/utils",
+    "registry/assets/activity-feed-avatar.png",
+    "registry/assets/avatars/avatar-01.jpg",
+    "registry/assets/images/art-01.jpg",
+    "registry.json",
+    "tokens/banhaten.tokens.json",
+    "schema",
+    "docs",
+    "banhaten.config.example.json",
+    "README.md",
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "SECURITY.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "npm --prefix playground ci --include=dev --include=optional && npm --prefix playground run build",
+    "build:railway": "npm --prefix playground ci --include=dev --include=optional && npm --prefix playground run build:railway",
+    "start": "node playground/scripts/serve-static.mjs playground/dist",
+    "check": "node --check src/cli/index.js && node --check src/cli/command-line.js && node --check src/cli/doctor.js && node --check src/cli/config-editors.js && node --check src/cli/source-scanner.js && node --check src/cli/jsonc.js && node --check src/cli/vite-config.js && node --check src/cli/install-plan.js && node --check src/cli/install-receipt.js && node --check src/cli/package-install-state.js && node --check src/cli/package-manager.js && node --check src/cli/package-plan.js && node --check src/cli/package-version.js && node --check scripts/compile-token-catalog.mjs && node --check scripts/sync-default-theme-neutral-values.mjs && node --check scripts/token-catalog-test.mjs && node --check scripts/registry-catalog.mjs && node --check scripts/generate-registry-index.mjs && node --check scripts/generate-shadcn-registry.mjs && node --check scripts/normalize-component-docs.mjs && node --check scripts/package-artifact.mjs && node --check scripts/check-package-contents.mjs && node --check scripts/select-react-compatibility.mjs && npm run contracts:check && npm run cli:test && npm run tokens:check && npm run components:ownership:check && npm run registry:check && npm run docs:check && npm run package:check && npm run playground:build && npm run playground:test:browser && npm run playground:audit",
+    "contracts:check": "node scripts/validate-contracts.mjs",
+    "cli:test": "node scripts/cli-argument-test.mjs && node scripts/cli-file-transaction-test.mjs && node scripts/cli-dependency-test.mjs && node scripts/cli-install-plan-test.mjs && node scripts/cli-integration-test.mjs && node scripts/cli-doctor-test.mjs",
+    "playground:build": "npm --prefix playground run build",
+    "playground:dev": "npm --prefix playground run dev",
+    "playground:test": "npm --prefix playground run test",
+    "playground:test:browser": "npm --prefix playground run test:browser",
+    "playground:audit": "npm --prefix playground audit --audit-level=high",
+    "package:check": "node scripts/generate-registry-index.mjs --check && node scripts/compile-token-catalog.mjs --check && node scripts/check-package-contents.mjs",
+    "registry:build": "node scripts/generate-registry-index.mjs --write",
+    "registry:check": "node scripts/generate-registry-index.mjs --check && node scripts/check-registry-mirrors.mjs && node scripts/generate-shadcn-registry.mjs --check && node scripts/registry-runtime-exports-test.mjs && node scripts/check-isolated-registry-installs.mjs --packed",
+    "registry:export": "node scripts/generate-registry-index.mjs --write && node scripts/generate-shadcn-registry.mjs --write",
+    "registry:exports": "node scripts/check-isolated-registry-installs.mjs --write-exports",
+    "registry:sync": "node scripts/check-registry-mirrors.mjs --write",
+    "components:tokens:check": "node scripts/check-component-token-usage.mjs",
+    "components:ownership:check": "npm --prefix playground run test:ownership",
+    "components:tokens:metadata": "node scripts/sync-component-token-metadata.mjs",
+    "docs:check": "node scripts/check-component-docs.mjs && node scripts/normalize-component-docs.mjs",
+    "docs:normalize": "node scripts/normalize-component-docs.mjs --write",
+    "smoke": "node src/cli/index.js list",
+    "tokens:aliases:check": "node scripts/sync-default-theme-neutral-values.mjs",
+    "tokens:aliases:sync": "node scripts/sync-default-theme-neutral-values.mjs --write",
+    "tokens:build": "npm run tokens:aliases:sync && node scripts/compile-token-catalog.mjs --write && node scripts/generate-token-css.mjs --write",
+    "tokens:check": "npm run tokens:aliases:check && node scripts/compile-token-catalog.mjs --check && node scripts/token-catalog-test.mjs && node scripts/generate-token-css.mjs --check && node scripts/check-token-css-reproducibility.mjs && node scripts/check-token-contract.mjs && npm run components:tokens:check && npm run components:tokens:metadata"
+  },
+  "engines": {
+    "node": ">=18.18"
+  },
+  "peerDependencies": {
+    "react": "^18.2.0 || ^19.0.0",
+    "react-dom": "^18.2.0 || ^19.0.0",
+    "tailwindcss": "^4.0.0"
+  },
+  "keywords": [
+    "banhaten",
+    "design-system",
+    "react",
+    "shadcn",
+    "rtl",
+    "arabic",
+    "components"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/AhmadGalal85/Banhaten-design-system.git"
+  },
+  "bugs": {
+    "url": "https://github.com/AhmadGalal85/Banhaten-design-system/issues"
+  },
+  "homepage": "https://github.com/AhmadGalal85/Banhaten-design-system/tree/main/docs",
+  "directories": {
+    "doc": "docs"
+  },
+  "author": "Ahmad Galal",
+  "dependencies": {
+    "ajv": "^8.20.0",
+    "minimatch": "^10.2.5",
+    "semver": "^7.8.5",
+    "yaml": "^2.9.0"
+  }
+}

package/registry/component-contract.json

@@ -1,40 +1,40 @@
-{
-  "capabilities": {
-    "actions": "Actions",
-    "alignments": "Alignments",
-    "breakpoints": "Breakpoints",
-    "cardPositions": "Card Positions",
-    "colors": "Colors",
-    "controlPositions": "Control Positions",
-    "densities": "Densities",
-    "directions": "Directions",
-    "features": "Features",
-    "forms": "Forms",
-    "indicators": "Indicators",
-    "intents": "Intents",
-    "itemKinds": "Item Kinds",
-    "itemTypes": "Item Types",
-    "kinds": "Kinds",
-    "labelPositions": "Label Positions",
-    "layouts": "Layouts",
-    "modes": "Modes",
-    "offsets": "Offsets",
-    "options": "Options",
-    "orientations": "Orientations",
-    "platforms": "Platforms",
-    "pointerPositions": "Pointer Positions",
-    "selectionTypes": "Selection Types",
-    "shapes": "Shapes",
-    "sides": "Sides",
-    "sizes": "Sizes",
-    "states": "States",
-    "statusColors": "Status Colors",
-    "styles": "Styles",
-    "tokens": "Tokens",
-    "tones": "Tones",
-    "types": "Types",
-    "valueModes": "Value Modes",
-    "variants": "Variants",
-    "widths": "Widths"
-  }
-}
+{
+  "capabilities": {
+    "actions": "Actions",
+    "alignments": "Alignments",
+    "breakpoints": "Breakpoints",
+    "cardPositions": "Card Positions",
+    "colors": "Colors",
+    "controlPositions": "Control Positions",
+    "densities": "Densities",
+    "directions": "Directions",
+    "features": "Features",
+    "forms": "Forms",
+    "indicators": "Indicators",
+    "intents": "Intents",
+    "itemKinds": "Item Kinds",
+    "itemTypes": "Item Types",
+    "kinds": "Kinds",
+    "labelPositions": "Label Positions",
+    "layouts": "Layouts",
+    "modes": "Modes",
+    "offsets": "Offsets",
+    "options": "Options",
+    "orientations": "Orientations",
+    "platforms": "Platforms",
+    "pointerPositions": "Pointer Positions",
+    "selectionTypes": "Selection Types",
+    "shapes": "Shapes",
+    "sides": "Sides",
+    "sizes": "Sizes",
+    "states": "States",
+    "statusColors": "Status Colors",
+    "styles": "Styles",
+    "tokens": "Tokens",
+    "tones": "Tones",
+    "types": "Types",
+    "valueModes": "Value Modes",
+    "variants": "Variants",
+    "widths": "Widths"
+  }
+}