@nadicodeai/ui 6.1.0 → 6.2.0

package/dist/components/forma-appearance.d.ts

@@ -0,0 +1,13 @@
+/**
+ * The stored appearance, reachable from a server. `forma-avatar.tsx` is a
+ * `"use client"` module, and under React Server Components every export of one
+ * becomes a client reference — a re-exported pure function included, which a
+ * server caller can only fail to invoke. A product whose server resolves an
+ * Agent's look before it renders the avatar (the Portal builds its rows that
+ * way) imports the resolver from here, and so does every other consumer: the
+ * avatar comes from `@nadicodeai/ui/components/forma-avatar`, the stored
+ * spelling from this module, and neither re-exports the other.
+ */
+export { type StoredAppearance, defaultShape, formaColorValues, resolveAppearance, shapeFor, } from "../internal/forma/stored-appearance.js";
+export { type FormaChoice, type FormaColor, type FormaForm, type FormaState, } from "../internal/forma/model.js";
+//# sourceMappingURL=forma-appearance.d.ts.map

package/dist/components/forma-appearance.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"forma-appearance.d.ts","sourceRoot":"","sources":["../../src/components/forma-appearance.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,OAAO,EACL,KAAK,gBAAgB,EACrB,YAAY,EACZ,gBAAgB,EAChB,iBAAiB,EACjB,QAAQ,GACT,MAAM,oCAAoC,CAAC;AAC5C,OAAO,EACL,KAAK,WAAW,EAChB,KAAK,UAAU,EACf,KAAK,SAAS,EACd,KAAK,UAAU,GAChB,MAAM,wBAAwB,CAAC"}

package/dist/components/forma-appearance.js

@@ -0,0 +1,11 @@
+/**
+ * The stored appearance, reachable from a server. `forma-avatar.tsx` is a
+ * `"use client"` module, and under React Server Components every export of one
+ * becomes a client reference — a re-exported pure function included, which a
+ * server caller can only fail to invoke. A product whose server resolves an
+ * Agent's look before it renders the avatar (the Portal builds its rows that
+ * way) imports the resolver from here, and so does every other consumer: the
+ * avatar comes from `@nadicodeai/ui/components/forma-avatar`, the stored
+ * spelling from this module, and neither re-exports the other.
+ */
+export { defaultShape, formaColorValues, resolveAppearance, shapeFor, } from "../internal/forma/stored-appearance.js";

package/dist/internal/forma/stored-appearance.d.ts

@@ -0,0 +1,29 @@
+import { type FormaChoice, type FormaColor } from "./model.js";
+/** What Hermes stores for an Agent's look. Both may be absent or unknown. */
+export interface StoredAppearance {
+    shape?: string | null;
+    color?: string | null;
+}
+/** The `shape` value a chosen form is stored as. */
+export declare const shapeFor: (form: FormaChoice) => string;
+/** The stored shape of the form an Agent wears until a customer chooses one. */
+export declare const defaultShape: string;
+/**
+ * The hex each palette colour is stored as. Hermes keeps an Agent's colour as
+ * a CSS colour for its own surfaces, so the stored spelling is a value rather
+ * than a token reference; `stored-appearance.test.ts` holds this table to the
+ * shipped design-system tokens, and the ESLint colour-literal exemption in the
+ * root config names this file.
+ */
+export declare const formaColorValues: Record<FormaColor, string>;
+/**
+ * Resolve the stored strings to what `FormaAvatar` draws. An unknown shape is
+ * the default form and an unknown colour is undefined, which leaves the form
+ * its own pigment. The root Agent is the caller's business: a caller that owns
+ * one passes `form="nadia"` instead of asking here.
+ */
+export declare function resolveAppearance(stored: StoredAppearance): {
+    form: FormaChoice;
+    color: FormaColor | undefined;
+};
+//# sourceMappingURL=stored-appearance.d.ts.map

package/dist/internal/forma/stored-appearance.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stored-appearance.d.ts","sourceRoot":"","sources":["../../../src/internal/forma/stored-appearance.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,WAAW,EAAE,KAAK,UAAU,EAA0C,MAAM,SAAS,CAAC;AAEpG,6EAA6E;AAC7E,MAAM,WAAW,gBAAgB;IAC/B,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CACvB;AAED,oDAAoD;AACpD,eAAO,MAAM,QAAQ,GAAI,MAAM,WAAW,KAAG,MAAyB,CAAC;AAEvE,gFAAgF;AAChF,eAAO,MAAM,YAAY,EAAE,MAA8B,CAAC;AAc1D;;;;;;GAMG;AACH,eAAO,MAAM,gBAAgB,EAAE,MAAM,CAAC,UAAU,EAAE,MAAM,CAOvD,CAAC;AAEF;;;;;GAKG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,gBAAgB,GAAG;IAC3D,IAAI,EAAE,WAAW,CAAC;IAClB,KAAK,EAAE,UAAU,GAAG,SAAS,CAAC;CAC/B,CAEA"}

package/dist/internal/forma/stored-appearance.js

@@ -0,0 +1,53 @@
+import { defaultForm, formaChoices, formaColors } from "./model.js";
+/** The `shape` value a chosen form is stored as. */
+export const shapeFor = (form) => `forma:${form}`;
+/** The stored shape of the form an Agent wears until a customer chooses one. */
+export const defaultShape = shapeFor(defaultForm);
+/**
+ * The five role names the launch Agents were stored under, each kept at the
+ * form it wore. Forms are shapes, never roles: nothing new is stored this way.
+ */
+const legacyShapes = new Map([
+    ["forma:research", "uovo"],
+    ["forma:build", "goccia"],
+    ["forma:design", "nuvola"],
+    ["forma:operate", "quadrato"],
+    ["forma:review", "esagono"],
+]);
+/**
+ * The hex each palette colour is stored as. Hermes keeps an Agent's colour as
+ * a CSS colour for its own surfaces, so the stored spelling is a value rather
+ * than a token reference; `stored-appearance.test.ts` holds this table to the
+ * shipped design-system tokens, and the ESLint colour-literal exemption in the
+ * root config names this file.
+ */
+export const formaColorValues = {
+    verde: "#00a85a",
+    cobalto: "#1e3cff",
+    rosso: "#d3302f",
+    arancio: "#ff5a1f",
+    giallo: "#ffc220",
+    avorio: "#e9e7db",
+};
+/**
+ * Resolve the stored strings to what `FormaAvatar` draws. An unknown shape is
+ * the default form and an unknown colour is undefined, which leaves the form
+ * its own pigment. The root Agent is the caller's business: a caller that owns
+ * one passes `form="nadia"` instead of asking here.
+ */
+export function resolveAppearance(stored) {
+    return { form: formFor(stored.shape), color: colorFor(stored.color) };
+}
+function formFor(shape) {
+    if (!shape)
+        return defaultForm;
+    // A Map, not an object: the shape is a stored string from a machine, and an
+    // object lookup would hand back `toString` or `constructor` for those spellings.
+    return (formaChoices.find((form) => shape === shapeFor(form)) ?? legacyShapes.get(shape) ?? defaultForm);
+}
+function colorFor(color) {
+    if (!color)
+        return undefined;
+    const stored = color.toLowerCase();
+    return formaColors.find((name) => stored === formaColorValues[name] || color === name);
+}

package/docs/forma-avatar.md

@@ -88,5 +88,23 @@ exposes `data-forma-avatar`, `data-state`, `data-color` on its host and
 `defaultForm`) are exported beside it for pickers and stored-appearance
 mapping; the geometry, rig and frame computation are internal.
 
+The stored appearance resolves in this package too, so every product draws one
+Agent the same way. `StoredAppearance` is the pair of strings a product stores, `shape`
+and `color`, either of which may be absent or unknown. `resolveAppearance`
+answers the `form` and `color` the avatar takes: an unknown shape is
+`defaultForm`, the five retired role shapes keep the form each one wore, and an
+unknown colour is `undefined`, which leaves the form its own pigment. A stored
+colour matches a palette hex in any case or the bare colour name.
+The resolver lives in `@nadicodeai/ui/components/forma-appearance`, which
+carries no `"use client"`: `FormaAvatar` is a client component, and a pure
+function re-exported from a client module becomes a client reference a server
+cannot call, so the two entry points do not re-export each other and every
+consumer imports the look from one and the avatar from the other.
+`shapeFor(form)` writes the stored spelling of a chosen form, `defaultShape` is
+`shapeFor(defaultForm)`, and `formaColorValues` is the hex each palette colour
+is stored as, held to the shipped design-system tokens by a test beside the
+resolver. The root Agent is the product's decision, not the resolver's: a
+product that owns one passes `form="nadia"` itself.
+
 Additions to the family go through this document and the design-system
 token contract, never through an ad-hoc visual.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nadicodeai/ui",
-  "version": "6.1.0",
+  "version": "6.2.0",
   "type": "module",
   "publishConfig": {
     "access": "public"
@@ -70,7 +70,7 @@
     "@assistant-ui/react": "0.15.18",
     "@assistant-ui/react-markdown": "0.14.14",
     "@base-ui/react": "^1.8.0",
-    "@nadicodeai/design-system": "6.1.0",
+    "@nadicodeai/design-system": "6.2.0",
     "@paper-design/shaders": "0.0.80",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",