@nadicodeai/ui 2.0.0 → 2.1.0

package/AGENTS.md

@@ -4,7 +4,10 @@ The `@nadicodeai/ui` npm workspace: the shared NadicodeAI React UI package on br
 
 ## Commands
 
-Proof escalates by the ladder in the root `AGENTS.md` "Commands": `npm run check -w @nadicodeai/ui` and `npm run test -w @nadicodeai/ui` before pushing. `test` builds `dist` first, then runs the workspace guards and the browser-free jsdom + axe-core tier-1 accessibility checks.
+Proof follows [the repository pipeline](../../docs/agents/develop.md#the-pipeline):
+`npm run check -w @nadicodeai/ui` and `npm run test -w @nadicodeai/ui` before
+pushing. `test` builds `dist` first, then runs the workspace guards and the
+browser-free jsdom + axe-core tier-1 accessibility checks.
 
 | Command | When |
 | --- | --- |
@@ -26,7 +29,7 @@ Proof escalates by the ladder in the root `AGENTS.md` "Commands": `npm run check
 | Motion behavior | `../design-system/DESIGN.md` "Motion", `src/lib/motion.ts`, then the `product-design` skill for agent procedure |
 | Which component subpaths exist | `package.json` `exports` (the `./components/*` wildcard over `src/components/` source is the whole surface. Never maintain a hand-copied list) |
 | shadcn / assistant-ui discovery | Live shadcn and assistant-ui CLIs (`npx shadcn@latest info\|search\|docs\|view\|add --dry-run`, `npx assistant-ui@latest add --help`). No committed registry inventory or snapshot exists, and `--overwrite` needs an explicit maintainer ask plus a reviewed diff |
-| Releasing / publishing | `../../docs/agents/npm-publishing.md` (release decision enforced by the pre-push gate, detail in `docs/contract.md`) |
+| Releasing / publishing | `../../docs/agents/publish.md` (release decision enforced by the pre-push gate, detail in `docs/contract.md`) |
 | Tokens, geometry, and the CSS the package composes | `../design-system/AGENTS.md` and `../design-system/DESIGN.md` |
 | Website page assembly | `../../apps/website/AGENTS.md` |
 | Portal screens | `../../apps/portal/AGENTS.md` |

package/docs/agents/nadicodeai-ui.md

@@ -36,7 +36,7 @@ Use shadcn MCP or the CLI live; never commit an upstream registry inventory.
 the committed package surface. Preview upstream changes before applying them;
 do not overwrite maintained source without explicit maintainer direction.
 
-The package [`AGENTS.md`](../../AGENTS.md) maps scoped commands. Proof escalates
-by the ladder in the repository's root `AGENTS.md` "Commands": this workspace's
+The package [`AGENTS.md`](../../AGENTS.md) maps scoped commands. Proof follows
+[the repository pipeline](../../../../docs/agents/develop.md#the-pipeline): this workspace's
 `check` and `test`, then the root `npm run check` and `npm run test` when the
 diff reaches other workspaces.

package/docs/contract.md

@@ -97,7 +97,7 @@ gone, is [`packages/design-system/DESIGN.md`, "## Status Vocabulary"](../../desi
 - **Agents is the client-only conversation interface.** `@nadicodeai/ui/agents` re-exports the complete `@assistant-ui/react` runtime and primitive API plus the reviewed, branded registry composition held under `src/internal/assistant-ui/`. Its built entry retains `"use client"`. Consumers receive Thread, attachments, Markdown, reasoning, tools, suggestions, providers, runtimes, hooks, and types from that one domain namespace. Agent identity components use their direct component subpaths so server compositions do not import the conversation runtime. The vendor name is not a public NadicodeAI subpath, and the package does not rename, wrap, or rebuild assistant-ui behavior.
 - **Base UI is the active primitive base.** `components.json` must resolve through a Base style, currently `base-nova`, and `npx shadcn@latest info --json` must report `base: "base"`. Do not reintroduce `radix-ui`, `@radix-ui/*`, or `vaul` to package source, dependencies, or app optimizer configuration. Registry-owned shadcn primitives stay aligned with current `shadcn@latest` Base UI output; use Base UI `render` composition instead of Radix `asChild`. `cmdk` is allowed only for the stock shadcn Command component while the current `base-nova` registry declares that dependency; do not use it elsewhere or replace it without a shadcn/compatibility decision and tests.
 - **Named shadcn blocks stay named.** When a user, plan, or issue selects a shadcn block/example such as `login-02`, `signup-02`, `dashboard-01`, or `sidebar-*`, use that registry item as the source of truth through shadcn CLI/MCP. Do not replace it with a package-authored abstraction unless the plan explicitly records the substitution, the reason, and the true consumer route that proves it.
-- **Public surface changes require a release decision.** Any change to exported components, `src/index.ts`, package `exports`, `globals.css`, theme behavior, package docs, package skills, or design-system token/CSS/theme output consumed by this package must end with an explicit npm release decision before handoff: bump the relevant version(s) and run `npm pack --dry-run -w @nadicodeai/ui` per `../../../docs/agents/npm-publishing.md`, or include a `[no-publish]` commit marker with the reason in the commit body. The pre-push gate requires one of the two. When the UI change depends on modified `@nadicodeai/design-system` output, bump and publish `@nadicodeai/design-system` first, then update this package's dependency and publish UI. Never claim a UI package change is shipped until `npm view @nadicodeai/ui version` reports the intended version.
+- **Public surface changes require a release decision.** Any change to exported components, `src/index.ts`, package `exports`, `globals.css`, theme behavior, package docs, package skills, or design-system token/CSS/theme output consumed by this package must end with an explicit npm release decision before handoff: bump the relevant version(s) and run `npm pack --dry-run -w @nadicodeai/ui` per `../../../docs/agents/publish.md`, or include a `[no-publish]` commit marker with the reason in the commit body. The pre-push gate requires one of the two. When the UI change depends on modified `@nadicodeai/design-system` output, bump and publish `@nadicodeai/design-system` first, then update this package's dependency and publish UI. Never claim a UI package change is shipped until `npm view @nadicodeai/ui version` reports the intended version.
 
 ## Admission Rules
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/ui",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "type": "module",
   "publishConfig": {
     "access": "public"
@@ -63,7 +63,7 @@
     "@assistant-ui/react": "0.15.1",
     "@assistant-ui/react-markdown": "0.14.8",
     "@base-ui/react": "^1.6.0",
-    "@nadicodeai/design-system": "2.0.0",
+    "@nadicodeai/design-system": "2.1.0",
     "@paper-design/shaders": "0.0.78",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",