@ekanos/cli 0.22.1 → 0.23.0

package/templates/harness/next.config.mjs.tmpl

@@ -6,10 +6,13 @@ import { fileURLToPath } from 'node:url';
 /**
  * The shell lives two directories below your project root and has no
  * node_modules of its own; `next`, `react` and `@ekanos/harness` all resolve
- * upward into yours. Pointing Next at that root stops it inferring a different
- * one and keeps file watching over your integration source.
+ * upward into yours. Inside a workspace (pnpm, npm or yarn workspaces, or an
+ * Ekanos repo) they live in the WORKSPACE root's node_modules instead, so this
+ * is that root. Pointing Next at it stops it inferring a different one, lets
+ * it follow the package manager's links, and keeps file watching over your
+ * source, which sits inside it.
  */
-const projectRoot = fileURLToPath(new URL('../../', import.meta.url));
+const turbopackRoot = fileURLToPath(new URL(__TURBOPACK_ROOT__, import.meta.url));
 
 /** @type {import('next').NextConfig} */
 const config = {
@@ -21,7 +24,7 @@ const config = {
   // and the harness renders in the system font stack, with no error.
   transpilePackages: ['@ekanos/harness'],
   turbopack: {
-    root: projectRoot,
+    root: turbopackRoot,
     resolveAlias: {
       // A widget written for the real Ekanos host imports
       // `useTeamAccountWorkspace()` to read `account.slug`. That module

package/templates/package.json.tmpl

@@ -12,12 +12,12 @@
     "prepare": "node scripts/setup-hooks.mjs"
   },
   "dependencies": {
-    "@ekanos/sdk": "^0.25.0",
-    "@ekanos/ui": "^0.25.0"
+    "@ekanos/sdk": "^0.26.0",
+    "@ekanos/ui": "^0.26.0"
   },
   "devDependencies": {
-    "@ekanos/cli": "^0.22.1",
-    "@ekanos/harness": "^0.25.0",
+    "@ekanos/cli": "^0.23.0",
+    "@ekanos/harness": "^0.26.0",
     "@hookform/resolvers": "^5.2.2",
     "@tailwindcss/postcss": "^4.3.3",
     "@tanstack/react-query": "^5.101.4",
@@ -34,6 +34,6 @@
     "tailwindcss": "^4.3.3",
     "typescript": "^5.9.3",
     "vitest": "4.1.10",
-    "zod": "^3.25.76"
+    "zod": "^4.6.7"
   }
 }

package/templates/skills/build-integration/references/widget-design.md

@@ -215,9 +215,8 @@ mock switch) so the harness can show all four; remove it before publish.
   state, `card`/`dialog`/`select`/`input` for the rest. Never hand-roll a
   button, input, select, label or status pill out of raw HTML elements;
   `ekanos validate` warns on each one. `cn()` from `@ekanos/ui/utils` for
-  conditional classes; icons through `@ekanos/ui/icon` (Font Awesome names —
-  they render empty outside a host that loads FA; that is expected in bare
-  tests).
+  conditional classes; icons through `@ekanos/ui/icon` (Phosphor names from
+  phosphoricons.com, such as `house`).
 - **No inline styles**: `style={{ … }}` escapes the theme entirely — no dark
   mode, no Source branding, no lint. Everything is a Tailwind class.
 

package/templates/skills/polish-widgets/references/patterns.md

@@ -1,8 +1,8 @@
 # Widget fix patterns — before → after
 
 Each pattern names the failure, then shows the smallest honest fix. All
-imports are `@ekanos/ui/*`; icons go through `@ekanos/ui/icon` (Font Awesome
-names — verify against the Free set). Everything sits inside the standard
+imports are `@ekanos/ui/*`; icons go through `@ekanos/ui/icon` (Phosphor
+names from phosphoricons.com). Everything sits inside the standard
 `Widget.Active` body from the SDK's compound API; these are the bodies, not
 the wrapper.
 
@@ -184,7 +184,7 @@ is not information-rich; it is unreadable.
 <div className="space-y-1 p-2">
   {events.map((e) => (
     <div key={e.id} className="flex gap-1 text-xs">
-      <Icon name="fa-bolt" className="h-3 w-3" />
+      <Icon name="lightning" className="h-3 w-3" />
       <span>{e.title}</span>
     </div>
   ))}
@@ -268,7 +268,7 @@ import {
     <DropdownMenuTrigger
       render={<Button variant="ghost" size="icon" className="h-8 w-8" />}
     >
-      <Icon name="fa-ellipsis-vertical" className="h-4 w-4" />
+      <Icon name="dots-three-vertical" className="h-4 w-4" />
     </DropdownMenuTrigger>
     <DropdownMenuContent align="end">
       <DropdownMenuItem>View details</DropdownMenuItem>
@@ -293,7 +293,7 @@ said, and it matches every other widget on the board:
 ```tsx
 // AFTER — the SDK's empty state, one sentence of what appears here
 <Widget.Empty
-  icon="fa-inbox"
+  icon="tray"
   title="No invoices yet"
   description="Invoices appear here as soon as your first one is issued."
 />

package/dist/generated/fa-free-names.d.ts

@@ -1,9 +0,0 @@
-export declare const FA_FREE_VERSION = "7.3.1";
-/** Every icon name Font Awesome Free ships — NOT Ekanos's set (Pro, a superset). */
-export declare const FA_FREE_ICON_NAMES: ReadonlySet<string>;
-/**
- * Hand-curated Pro-only name → nearest Free alternative, sourced from
- * @ekanos/ui's Pro→Free glyph map. Not exhaustive — a Pro-only name with
- * no entry there has no known Free substitute here.
- */
-export declare const FA_PRO_TO_FREE_HINTS: ReadonlyMap<string, string>;