@nadicodeai/design-system 12.1.164 → 12.1.166

package/AGENTS.md

@@ -12,15 +12,15 @@ usage page in its source; `examples/` contains rendered specimens.
 - Terms: `GLOSSARY.md`. Static consumption: `README.md`.
 - React consumption: `../ui/README.md`.
 - Visual checks: `playwright.visual.config.ts` and `tests/visual/`, run by
-  post-merge's `test (website, packages)` job. Its `-linux` baselines are what the
+  post-merge's `test (website)` job. Its `-linux` baselines are what the
   CI runner image (`../../tools/ci/host/Dockerfile`) renders: after an intended
-  visual change, rerun `npm run test:visual -w @nadicodeai/design-system --
-  --update-snapshots` inside that image and commit the new screenshots.
+  visual change, rerun `pnpm --filter @nadicodeai/design-system test:visual --update-snapshots`
+  inside that image and commit the new screenshots.
 - Releases: `../../docs/agents/publish.md`.
 
 Edit token sources (the four groups in `DESIGN.md`'s front matter, every other
 value in `src/tokens/extension.tokens.json`), then run
-`npm run build -w @nadicodeai/design-system`. Generated CSS and `dist/`
+`pnpm --filter @nadicodeai/design-system build`. Generated CSS and `dist/`
 are outputs, not hand-edited sources. Favicon source changes use
 `generate:favicons`; a lucide-static upgrade uses `generate:icons`.
 `package.json` owns the commands; shared validation policy is in

package/DESIGN.md

@@ -539,7 +539,7 @@ The products are assembled in three layers, each with one owner and one check, s
 
 - **Components.** Every component in `@nadicodeai/ui` has a usage page: when to use it, what to use instead, how it behaves, its words and its accessibility, written in the component's own source and rendered by the package's showcase ("Component selection and usage").
 - **Compositions.** A page is built from one of nine compositions, each a component in `@nadicodeai/ui` with fixed slots, so the page supplies only content and the order of its actions and the place of its three dots cannot drift: the five page compositions, the record row, the empty state, the overlays and the identity marks ("Page compositions").
-- **Checks.** Four lint rules fail the build in the Portal, Nadia's window and Alveare Server: a page renders a composition (`page-composition`), an absence is only `EmptyState` (`empty-state-owner`), commands go only through `PageActions`, `ActionMenu` and `AccountMenu` (`menu-owner`, with the menu modules held by `no-restricted-imports`), and a title or a label carries no icon (`no-decorative-icon`). A page that broke a rule when the checks arrived sits on its product's recorded baseline, whose count may only fall.
+- **Checks.** Three lint rules fail the build in the Portal, Nadia's window and Alveare Server: a page renders a composition (`page-composition`), an absence is only `EmptyState` (`empty-state-owner`), and a title or a label carries no icon (`no-decorative-icon`).
 
 One foundation serves four registers. The foundation is every value in this file. A register is one product's way of applying it: the website, the Portal, the Nadia desktop app and the Alveare desktop app ("Registers"). A register adds rules and chooses which values it uses; it never redefines a value or mints one. A value one register needs is authored here under `register.<name>`, and a value two registers share moves to `core`.
 
@@ -559,7 +559,7 @@ The neutral spine carries grounds, chrome, text and every control: `{colors.ink}
 
 ### Colour as stage
 
-The identity palette is the brand's colour: cobalto `{colors.identity-cobalto}`, verde `{colors.identity-verde}`, arancio `{colors.identity-arancio}`, giallo `{colors.identity-giallo}` and rosso `{colors.identity-rosso}`, with `{colors.identity-ink}` and `{colors.identity-white}` as the poles type sits on. Azzurro `{colors.identity-azzurro}` has two jobs: the first stripe of Nadia's ribbon, and a band of a company's card foil ("Company card").
+The identity palette is the brand's colour: cobalto `{colors.identity-cobalto}`, verde `{colors.identity-verde}`, arancio `{colors.identity-arancio}`, giallo `{colors.identity-giallo}` and rosso `{colors.identity-rosso}`, with `{colors.identity-ink}` and `{colors.identity-white}` as the poles type sits on. Azzurro `{colors.identity-azzurro}` has three jobs: the first stripe of Nadia's ribbon, the inner stripe of Alveare's mark ("Brand media authority"), and a band of a company's card foil ("Company card").
 
 The hues appear at full strength and flat, with no tints, steps, gradients or hover variants, in these places. The one exception is the website's shader objects, each the material of one object and never a section's ground: the threads she holds, a fan of lines in her stripes from her orb to her colleagues, on black; Alveare's hive, cells that light in its hues as the work passes; and the company card's holographic foil ("Company card"). Stripes and cells stay pure bands of their hues, never a colour between two of them. Ruled by the founder: "shaders are not backgrounds all over the place".
 
@@ -568,7 +568,7 @@ The hues appear at full strength and flat, with no tints, steps, gradients or ho
 - **Accents on the website.** A 2 px rule that marks one item of a set, one hue per item.
 - **Agents.** The orbs ("Agent orbs").
 - **Objects.** The saturated pieces of the art direction's objects, one per benefit ("Iconography").
-- **The logo.** The dot of the wordmark and the icon tile ("Brand media authority"), and the compact company identity marks ("Identity marks").
+- **The logo.** The dot of the wordmark, the icon tile and Alveare's striped mark ("Brand media authority"), and the compact company identity marks ("Identity marks").
 - **Imagery.** Art direction reads these tokens and keeps no private palette.
 
 Text on a colour ground is the pole that clears AA on that hue: `{colors.identity-white}` on cobalto and rosso; `{colors.identity-ink}` on verde, arancio and giallo. A control on a colour ground uses the button's on-colour variants ("Components"). Product chrome in the Portal and Nadia stays neutral: grounds, text, lines and navigation, a selected row included, whatever it opens. Colour inside that structure is the identity palette at full strength in both themes: the primary control and the on switch in cobalto, feedback and state in cobalto, verde, giallo and rosso with their pole for text, and links in cobalto, the dark theme's links and coloured text one light step of the same hue. It also identifies Agents, providers and categories; an Agent's own colour is her orb, so her row in a list never takes a hue. Choose a typed component tone from the semantic palette; never paint a control with an arbitrary identity hex.
@@ -780,7 +780,7 @@ Nadia's window, its list, its Settings and its side panel are Nadia's register (
 
 ### Page compositions
 
-A product page is one of five page compositions, each answering one question first and each one component in `@nadicodeai/ui` that draws its order, variants and states from the content the page gives it. A page renders one of them and never assembles its own header, toolbar, table, rows, menus or column; `page-composition` refuses a page that renders a part a composition owns:
+A product page is one of five page compositions, each answering one question first and each one component in `@nadicodeai/ui` that draws its order, variants and states from the content the page gives it. A page renders one of them and never assembles its own header, toolbar, table, rows, menus or column:
 
 | Composition | Owner | First answer | Structure |
 | --- | --- | --- | --- |
@@ -835,7 +835,7 @@ The owner approved the materials: Vercel's surfaces with a little more depth on
 
 **Product views on the website** preserve the real interface. Nadia uses captures of the running application, with the unchanged full-size image linked and capture provenance recorded in the repository, following the founder's 12 October correction of invented UI. Portal and Alveare may use inert scenes built from real components with fictional example data recorded in the repository. Never invent interface controls or frame a view in a device mockup. A product window takes the raised height on its ground; a card that overlaps it floats. Live components use dark mode in a black section; captures preserve the application's captured theme.
 
-Absence follows its container, and only a first use has a picture. In every product, the Portal included, a collection's first use shows its section's picture, and every other kind of absence goes without one. A picture sits on a working screen only there: never in a populated collection, a row or any other card; whole-page moments keep theirs ("Entry screens"). A page or region absence is a resting card with its own edge, never a dashed boundary; an absence inside a card is unframed, because the card already owns the edge, and `CollectionPage` puts every absence it draws in its card. `EmptyState` is the only owner of an absence: nothing else draws one (`empty-state-owner`), its `scope` (`page`, `region` or `card`) sets that frame, and it has no presentation option, so every product draws each kind the same way. A composition takes its absences as props (`empty`, `noMatch`, `failed`), as a `DataTable` takes `empty`. Its kind names the cause, and `EmptyState`'s usage page holds what each kind draws: `firstUse` (a collection with no records yet: its section's picture from the approved set in `@nadicodeai/design-system/assets/empty`, which [the art direction](../../skills/design/art-direction/references/surfaces.md#the-empty-state-set) keeps, and the one action that adds the first record, which the page's title row also keeps as its filled primary; a create action carries the leading +), `nothingYet`, `noResults`, `cleared`, `denied` and `failed`; a card-sized failure is `failed` with `scope="card"`, and there is no `ErrorCard`.
+Absence follows its container, and only a first use has a picture. In every product, the Portal included, a collection's first use shows its section's picture, and every other kind of absence goes without one. A picture sits on a working screen only there: never in a populated collection, a row or any other card; whole-page moments keep theirs ("Entry screens"). A page or region absence is a resting card with its own edge, never a dashed boundary; an absence inside a card is unframed, because the card already owns the edge, and `CollectionPage` puts every absence it draws in its card. `EmptyState` is the only owner of an absence: nothing else draws one, its `scope` (`page`, `region` or `card`) sets that frame, and it has no presentation option, so every product draws each kind the same way. A composition takes its absences as props (`empty`, `noMatch`, `failed`), as a `DataTable` takes `empty`. Its kind names the cause, and `EmptyState`'s usage page holds what each kind draws: `firstUse` (a collection with no records yet: its section's picture from the approved set in `@nadicodeai/design-system/assets/empty`, which [the art direction](../../skills/design/art-direction/references/surfaces.md#the-empty-state-set) keeps, and the one action that adds the first record, which the page's title row also keeps as its filled primary; a create action carries the leading +), `nothingYet`, `noResults`, `cleared`, `denied` and `failed`; a card-sized failure is `failed` with `scope="card"`, and there is no `ErrorCard`.
 
 A persistent notice sits in the section it concerns, action feedback is a toast, and field validation stays with its field. A notice has no close button: it stays until the state changes, and one note stands for one concept. A section notice is `MessageNotice`; a condition of the page's own object that the page itself resolves, such as a past-due subscription on its billing page, is a `NoticeBanner` carrying that fix; a failure the person must handle is never a toast alone but a very short toast beside a persistent notice. A condition of the system, the setup or the staff (a connection, a stored secret, a failing job, anything a staff member fixes in settings) is a notification in the product's inbox (in the Portal, the bell beside the account at the sidebar's foot), as Vercel keeps certificate, domain and integration alerts in its dashboard's notifications popover ([Vercel's notifications](https://vercel.com/docs/notifications)). It is never a banner on the pages, the Dashboard or the frame they share; the page that fixes it shows the state in its own section. The frame's one strip marks the Portal's Impersonation, because everything done during it is recorded as the Customer's member. A notice, a failed read, a confirmation's error and a toast each show a message its product's catalogue worded, never a sentence written where it shows ([the decision](../../docs/adr/2026-10-08-every-message-a-customer-reads-is-a-code-its-products-catalogue-words.md)). Each wraps a long word, never truncates, closes its title with a full stop before a body that follows on the same line, and shows a body only when it says more than the title; their usage pages hold how each draws it.
 
@@ -926,7 +926,7 @@ Every example and consuming surface covers its reachable populated, empty, loadi
 | [Book](https://vercel.com/geist/book) | `Card` + `AspectRatio` and cover artwork; no book-frame export |
 | [Breadcrumbs](https://vercel.com/geist/breadcrumbs) | The `Breadcrumb` family |
 | [Browser](https://vercel.com/geist/browser) | `Card` + `AspectRatio` and decorative browser chrome; `DesktopShell` stays real product chrome |
-| [Button](https://vercel.com/geist/button) | `Button`, `ButtonLink` and `buttonVariants` |
+| [Button](https://vercel.com/geist/button) | `Button` and `ButtonLink` |
 | [Calendar](https://vercel.com/geist/calendar) | `Calendar`; `DateRangeControl` for a metric's window |
 | [Checkbox](https://vercel.com/geist/checkbox) | `Checkbox` with the Field parts |
 | [Choicebox](https://vercel.com/geist/choicebox) | `ChoiceboxGroup` |
@@ -952,13 +952,13 @@ Every example and consuming surface covers its reachable populated, empty, loadi
 | [File Tree](https://vercel.com/geist/file-tree) | `SidebarMenu` + `Collapsible` + `FileTypeIcon` can follow sidebar-11 for nested files |
 | [Gauge](https://vercel.com/geist/gauge) | `Gauge` |
 | [Grid](https://vercel.com/geist/grid) | Layout grid, `CardRow`, website `nc-page`; no ruled `Grid` API |
-| [Input](https://vercel.com/geist/input) | `Input`; `InputGroup` for parts inside the box; `Field` or `SettingsField` for the card around it |
+| [Input](https://vercel.com/geist/input) | `Input`, with `prefix` and `suffix` for parts inside the box (`InputGroup` stays inside `@nadicodeai/ui`); `Field` or `SettingsField` for the card around it |
 | [JSON View](https://vercel.com/geist/json-view) | Composition for static JSON: code display with exact serialized text |
 | [Keyboard Input](https://vercel.com/geist/keyboard-input) | `Kbd` |
 | [Label](https://vercel.com/geist/label) | `Label`, `FieldLabel` and `FieldLegend` |
 | [Load More Button](https://vercel.com/geist/load-more-button) | `LoadMoreButton` |
 | [Loading Dots](https://vercel.com/geist/loading-dots) | `Button`'s `loading` and `WaitingLine`; no LoadingDots |
-| [Menu](https://vercel.com/geist/menu) | `ActionMenu`, `ActionContextMenu`, `PageActions`' `menu` and `AccountMenu`; the `DropdownMenu` family directly only for a choice menu such as a sort |
+| [Menu](https://vercel.com/geist/menu) | `ActionMenu`, `ActionContextMenu`, `PageActions`' `menu`, `AccountMenu` and the website's `SiteMenu`; the `DropdownMenu` family stays inside `@nadicodeai/ui`, which draws a choice menu such as a sort with it |
 | [MiddleTruncate](https://vercel.com/geist/middle-truncate) | `MiddleTruncate` |
 | [Modal](https://vercel.com/geist/modal) | The `Dialog` family, `FormDialog` for a short form and `ConfirmDialog` for a consequence |
 | [Multi Select](https://vercel.com/geist/multi-select) | `MultiSelect`; `Combobox multiple` when typing to find matters more; `CollectionFilters` for query facets |
@@ -1067,7 +1067,7 @@ A card or settings section is composed around a real task, collection or form; i
 
 ### Menus and commands
 
-A record's primary destination is its visible name or a labelled link. Navigation is never hidden in its action menu. Keep the main task visible: Edit opens the record inside its row, as in Vercel Domains; Connect belongs beside an available connection. Additional mutations use an end-aligned `ActionMenu`, the same commands on a right-click through `ActionContextMenu`; a menu is not required when the row has no secondary mutations. Commands reach a person only through `PageActions` (a page), `ActionMenu` and `ActionContextMenu` (a record) and `AccountMenu` (the account), each taking its commands as data (`menu-owner`). A menu names the record it acts on, keeps a command that cannot run in place with its reason, and puts the destructive command last after a divider; `ActionMenu`'s usage page holds how it draws them, and `AccountMenu`'s the account menu's one exception. A destructive command never becomes the loudest repeated action: it is never a button on every row.
+A record's primary destination is its visible name or a labelled link. Navigation is never hidden in its action menu. Keep the main task visible: Edit opens the record inside its row, as in Vercel Domains; Connect belongs beside an available connection. Additional mutations use an end-aligned `ActionMenu`, the same commands on a right-click through `ActionContextMenu`; a menu is not required when the row has no secondary mutations. Commands reach a person only through `PageActions` (a page), `ActionMenu` and `ActionContextMenu` (a record) and `AccountMenu` (the account), each taking its commands as data. A menu names the record it acts on, keeps a command that cannot run in place with its reason, and puts the destructive command last after a divider; `ActionMenu`'s usage page holds how it draws them, and `AccountMenu`'s the account menu's one exception. A destructive command never becomes the loudest repeated action: it is never a button on every row.
 
 Choose the surface by where the thing being changed is shown and how big the job is, never by the page that happens to need it: the same job takes the same surface in every product. Adding a skill is the catalogue drawer in the Portal and in Nadia, and editing a task or an MCP server opens its row in both. Each surface has one owner:
 
@@ -1089,7 +1089,7 @@ Collection search and filters stay immediately above their rows. The title row h
 
 ### Tables and missing values
 
-`Table`, `DataTable`, `TableCard`, `RecordList`, `Item` and `Tag` hold their geometry, columns and rows on their usage pages; `page-composition` refuses a `DataTable` without column headings. No heading sorts the rows, so no heading is a button: the page holds the order, through a `CollectionSort` above the list, and `aria-sort` marks the column the rows follow.
+`Table`, `DataTable`, `TableCard`, `RecordList`, `Item` and `Tag` hold their geometry, columns and rows on their usage pages; a `DataTable` has column headings. No heading sorts the rows, so no heading is a button: the page holds the order, through a `CollectionSort` above the list, and `aria-sort` marks the column the rows follow.
 
 A collection fits its container without sideways scrolling, and on a phone a row keeps its name above supporting facts that wrap in full, never a stack of labelled values, where a status keeps its own mark; `DataTable`'s and `RecordList`'s usage pages hold how their columns give way. Text anywhere in the product breaks between words, and inside a word only when that word alone cannot fit a line; a machine string such as a hash or a key breaks at any character in wrapped text, or is cut in the middle with `MiddleTruncate` on one line.
 
@@ -1185,7 +1185,7 @@ Three icons are the house's own, drawn on Lucide's grid in the same render: `arc
 
 The blue category uses the cobalto 200 ground and cobalto 1000 ink through `category-blue` and `category-blue-foreground`, with the same ramp steps in each theme. It never uses the status roles `info` or `info-soft`.
 
-An icon belongs to a control or a menu row, never to a title. A card's, a section's or a label's title and a KPI's label carry no icon (`no-decorative-icon`): an icon there repeats the words beside it and competes with the marks that matter. A menu row takes one icon, leading its label; a button takes one, leading or trailing it (`prefix` or `suffix`). A mark goes where it says which thing you are looking at; a picture marks a moment. Where each goes:
+An icon belongs to a control or a menu row, never to a title. A card's, a section's or a label's title and a KPI's label carry no icon: an icon there repeats the words beside it and competes with the marks that matter. A menu row takes one icon, leading its label; a button takes one, leading or trailing it (`prefix` or `suffix`). A mark goes where it says which thing you are looking at; a picture marks a moment. Where each goes:
 
 | Place | Identity mark | Icon | Picture |
 | --- | --- | --- | --- |
@@ -1209,7 +1209,9 @@ The company is **nadicode**, lowercase. Its logo is the n, and the name drawn in
 1. **Mark.** The n, the logo itself, as tall as it is wide, with nothing added. It stands for the company wherever the company is recognised by its sign: app headers and compact navigation, the corner of a slide, a sticker, a stamp.
 2. **Wordmark.** nadicode in one geometric line with one dot over the i. The dot is the only colour in the logo, where an Agent sits. Use it wherever the company is named: the website's header, documents, proposals, invoices, email signatures, a first slide.
 3. **Icon.** The mark on a tile with rounded corners, in one of three fields. The brand tile, the white n on `{colors.identity-cobalto}`, is for favicons, avatars and the website's app icon, and is the one place the brand colour fills a logo's field. Where the platform crops the picture itself, a profile picture cut to a circle or a square and a phone's home screen, the tile has square corners and the platform draws its shape: the avatar is the brand tile, or the light or dark tile where a profile wants white or black, with the n across 46% of the side, so a circle cut keeps it whole with its clear space. The mark is never a profile picture: it has no field, and its n runs to the edges a crop cuts. The light tile, the `{colors.ink}` n on white, is a desktop app's icon, which keeps it in the system's dark appearance. The dark tile, the white n on `{colors.identity-ink}`, is the icon wherever else it sits on a dark ground: a dark slide, an app's own dark screen.
-4. **Signature form.** The light tile with its construction guides in `{colors.logo-guide}`: a dotted circle around the arch whose radius is the golden section of the n's width, the two centre axes, and the n's width and height, each measured 1.000. It is drawn from 128 px up, on light grounds: Nadia's desktop icon, a cover or closing slide, a poster, print; on a dark ground the dark tile stands in for it. Below 128 px a guide is a fraction of a pixel, so the icon drops them; drawn on a screen as a logo, such as at the top of an entry scene, it drops them at any size. Alveare draws its own mark's desktop icon the same way.
+4. **Signature form.** The light tile with its construction guides in `{colors.logo-guide}`: a dotted circle around the arch whose radius is the golden section of the n's width, the two centre axes, and the n's width and height, each measured 1.000. It is drawn from 128 px up, on light grounds: Nadia's desktop icon, a cover or closing slide, a poster, print; on a dark ground the dark tile stands in for it. Below 128 px a guide is a fraction of a pixel, so the icon drops them; drawn on a screen as a logo, such as at the top of an entry scene, it drops them at any size.
+
+Alveare's mark is its own, chosen by the founder: the AV line, nadicode's n arch running down into a V's cup, drawn as a ribbon of six flat stripes 7 units wide, from the outside of the arch in: cobalto in its dark step (`{colors.dark-logo-dot}`), arancio, verde, rosso, giallo, azzurro. Six lanes running as one line are the hive. It sits on the dark tile everywhere, the app icon included, since Alveare opens onto black, and on a black screen it stands alone without its tile. Alveare Server's mark is the same ribbon turned and mirrored into an S. Both are drawn in `apps/alveare/brand/icons/`.
 
 The mark and the wordmark never stand side by side: the wordmark already begins with the n, so together they read "n nadicode". Each place takes one of them.
 

package/README.md

@@ -106,7 +106,7 @@ Consumer overrides belong in an explicit later layer:
 
 ## How the build works
 
-`npm run build -w @nadicodeai/design-system` reads two sources: the
+`pnpm --filter @nadicodeai/design-system build` reads two sources: the
 `@google/design.md` CLI exports `DESIGN.md`'s YAML front matter, and
 `scripts/sd/token-extension.ts` reads the token extension, `src/tokens/extension.tokens.json`.
 `scripts/sd/compose-token-graph.ts` joins them into the single `nadicode` token
@@ -125,7 +125,7 @@ host with base styles of its own). `src/css/index.css` declares the cascade's
 layer order.
 Generated files and `dist/` are outputs, which git does not track: edit
 `DESIGN.md` or `src/tokens/extension.tokens.json` and rebuild, never the output.
-Every install builds them through the root `prepare`, and `tests/guards/` holds
+A worktree's preparation and every CI job's setup build them, and `tests/guards/` holds
 the structural checks on every output.
 The favicons are the exception: `generate:favicons` writes them and git tracks
 them. A consumer reaches any output through the package's `exports`, never a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/design-system",
-  "version": "12.1.164",
+  "version": "12.1.166",
   "type": "module",
   "publishConfig": {
     "access": "public"
@@ -233,44 +233,36 @@
   "engines": {
     "node": ">=22"
   },
-  "scripts": {
-    "build": "tsx scripts/build.ts",
-    "generate:icons": "tsx scripts/generate-icons.ts",
-    "generate:favicons": "tsx scripts/generate-favicons.ts",
-    "lint:design": "design.md lint DESIGN.md",
-    "lint": "npm run lint:oxlint && node ../../tools/workspace/heavy-slots.mjs -- eslint --max-warnings=0",
-    "lint:oxlint": "node ../../tools/workspace/heavy-slots.mjs -- oxlint",
-    "typecheck": "node ../../tools/workspace/heavy-slots.mjs -- node ../../node_modules/typescript-native/bin/tsc --checkers 2 -p tsconfig.json",
-    "check": "npm run lint:design && npm run lint && npm run typecheck",
-    "check:static": "npm run check",
-    "test": "node ../../tools/workspace/heavy-slots.mjs --skip-if-filtered -- vitest run",
-    "test:visual": "node ../../tools/workspace/heavy-slots.mjs -- playwright test --config playwright.visual.config.ts",
-    "capture:geist": "node scripts/capture-geist.mjs",
-    "prepublishOnly": "npm run build"
-  },
   "devDependencies": {
     "@google/design.md": "0.4.0",
-    "@nadicodeai/eslint-config": "*",
-    "@nadicodeai/eslint-plugin": "*",
-    "@nadicodeai/oxlint-config": "*",
-    "@nadicodeai/static-design-server": "*",
-    "@nadicodeai/test-support": "*",
+    "@nadicodeai/static-design-server": "0.0.0",
+    "@nadicodeai/test-support": "0.0.0",
     "@playwright/test": "^1.64.1",
     "@types/node": "^24",
     "ajv": "8.20.0",
     "ajv-formats": "3.0.1",
     "esbuild": "^0.28.2",
-    "eslint": "^9.39.4",
     "lucide-static": "1.58.0",
-    "oxlint": "1.88.0",
-    "parse5": "^8.0.1",
     "postcss": "^8.5.30",
-    "postcss-value-parser": "^4.2.0",
+    "publint": "^0.3.25",
     "sharp": "^0.35.5",
     "style-dictionary": "^5.6.1",
     "tsx": "^4.23.15",
     "typescript": "^6",
     "typescript-native": "npm:typescript@7.0.2",
     "vitest": "^5.0.5"
+  },
+  "scripts": {
+    "build": "tsx scripts/build.ts",
+    "capture:geist": "node scripts/capture-geist.mjs",
+    "check:package": "publint --strict",
+    "generate:favicons": "tsx scripts/generate-favicons.ts",
+    "generate:icons": "tsx scripts/generate-icons.ts",
+    "lint": "oxlint -c ../../oxlint.config.ts",
+    "lint:design": "design.md lint DESIGN.md",
+    "lint:types": "oxlint -c ../../oxlint.types.config.ts",
+    "test": "vitest run",
+    "test:visual": "playwright test --config playwright.visual.config.ts",
+    "typecheck": "node node_modules/typescript-native/bin/tsc --checkers 2 -p tsconfig.json"
   }
-}
+}