@intelligo-dev/cli 1.0.0-beta.13 → 1.0.0-beta.14

package/templates/registry-items.json

@@ -74,7 +74,7 @@
     },
     "payment-poll": {
       "title": "QR Payment (poll)",
-      "description": "The non-card checkout the catalogue was missing: issue an invoice, show a QR the user scans in their banking app, poll until the provider confirms. Provider-agnostic — QPay, SocialPay, PIX, UPI, PromptPay all fit — through the lib/local-payment.ts binding. Requires the pricing item for lib/billing-config.ts's CURRENCY."
+      "description": "The non-card checkout the catalogue was missing: issue an invoice, show a QR the user scans in their banking app, poll until the provider confirms. Provider-agnostic — QPay, SocialPay, PIX, UPI, PromptPay all fit — with the invoice recorded and a paid one granted on the server; lib/local-payment.ts says what each reference costs and grants. Requires the pricing item for lib/billing-config.ts's CURRENCY."
     },
     "profile-settings": {
       "title": "Profile Settings",

package/templates/registry-requires.json

@@ -1,5 +1,5 @@
 {
-  "$comment": "Machine-readable requirements of every registry item \u2014 what shadcn's schema cannot express. `scaffold`: consumer files `intelligo create` provides that items may import. Per item: `marker` (the file whose presence means the item is installed), `items` (sibling items that ship files this one imports \u2014 install them first), `files` (scaffold files it imports), `exports` (names a scaffold file must export), `features` (feature keys the item gates on; register them in lib/plans.ts). tests/architecture/registry.test.ts asserts this file matches the code; CI derives the install order from it; `intelligo doctor` checks an app against it (packages/cli/templates/registry-requires.json is a copy the CLI build regenerates; the suite fails if it is stale).",
+  "$comment": "Machine-readable requirements of every registry item \u2014 what shadcn's schema cannot express. `scaffold`: consumer files `intelligo create` provides that items may import. Per item: `marker` (the file whose presence means the item is installed), `items` (sibling items that ship files this one imports \u2014 install them first), `files` (scaffold files it imports), `exports` (names a scaffold file must export), `features` (feature keys the item gates on; register them in lib/plans.ts). `seams`: files an item ships once and the deployment then owns, each with what it configures \u2014 `intelligo sync` never overwrites one, and message files (`messages/`) are merged key by key, the deployment's copy winning. tests/architecture/registry.test.ts asserts this file matches the code; CI derives the install order from it; `intelligo doctor` checks an app against it (packages/cli/templates/registry-requires.json is a copy the CLI build regenerates; the suite fails if it is stale).",
   "scaffold": [
     "lib/intelligo",
     "lib/plans",
@@ -8,6 +8,30 @@
     "i18n/routing",
     "i18n/navigation"
   ],
+  "seams": {
+    "lib/shell-config.tsx": "shell banner and header slots",
+    "lib/nav-config.ts": "navigation",
+    "lib/settings-nav.ts": "settings tabs",
+    "lib/error-reporting.ts": "the error reporter",
+    "lib/billing-config.ts": "product slug, currency, credit bundles",
+    "lib/feature-catalog.ts": "feature names and plans",
+    "lib/feature-gating-config.ts": "upgrade targets for gated features",
+    "lib/trial-banner-config.ts": "trial banner target and suppressed routes",
+    "lib/payment-poll-config.ts": "payment polling behaviour",
+    "lib/local-payment.ts": "the local payment provider",
+    "lib/onboarding-steps.ts": "onboarding steps",
+    "lib/dashboard-config.tsx": "dashboard copy",
+    "lib/dashboard-data.ts": "dashboard resume data",
+    "lib/document-patterns.ts": "artifact detection",
+    "lib/chat-model.ts": "the deployment's model",
+    "lib/chat-models.ts": "the models the composer offers",
+    "lib/chat-renderers.tsx": "tool-call renderers",
+    "lib/chat-canvas-config.tsx": "canvas editors per document kind",
+    "lib/chat-config.tsx": "agent identity, starters, header slot",
+    "lib/chat-server-config.ts": "the chat transport's configuration",
+    "lib/chat-widget-config.tsx": "the embedded widget",
+    "lib/notification-types.tsx": "icons for the product's notification types"
+  },
   "items": {
     "smoke": {
       "marker": "app/[locale]/registry-smoke/page.tsx"
@@ -102,7 +126,7 @@
     "profile-settings": {
       "marker": "app/[locale]/(app)/settings/profile/page.tsx",
       "items": ["route-error"],
-      "files": ["i18n/navigation"]
+      "files": ["i18n/navigation", "i18n/routing"]
     },
     "onboarding": {
       "marker": "app/[locale]/onboarding/layout.tsx",

package/templates/vitest/server-only.ts.tpl

@@ -0,0 +1,7 @@
+/**
+ * Stands in for the `server-only` package under Vitest (vitest.config.ts
+ * aliases it here). The real module throws outside a `react-server`
+ * build, which would fail every test that imports server code on the
+ * guard instead of on what it tests.
+ */
+export {};

package/templates/vitest/vitest.config.ts.tpl

@@ -0,0 +1,37 @@
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+import { defineConfig } from "vitest/config";
+
+const root = path.dirname(fileURLToPath(import.meta.url));
+
+/**
+ * The app's test runner.
+ *
+ * - `@` resolves the way the app's tsconfig resolves it.
+ * - `server-only` throws unless the bundler applies React's
+ *   `react-server` condition, which a test does not; the stub stands in
+ *   for it so a test can import server code.
+ * - The `@intelligo-dev/*` packages ship compiled ESM that imports
+ *   `server-only` itself. Vitest leaves node_modules to Node, where the
+ *   alias above never applies, so they are inlined: transformed by
+ *   Vitest like the app's own source, with the alias in effect.
+ */
+export default defineConfig({
+  resolve: {
+    alias: {
+      "@": root,
+      "server-only": path.join(root, "tests/stubs/server-only.ts"),
+    },
+  },
+  test: {
+    environment: "node",
+    include: ["**/*.test.{ts,tsx}"],
+    exclude: ["node_modules/**", ".next/**"],
+    server: {
+      deps: {
+        inline: [/node_modules\/@intelligo-dev\//],
+      },
+    },
+  },
+});