@eventcatalog/core 5.0.0-beta.9 → 5.0.0

package/dist/chunk-CA6WCQ2T.js

@@ -0,0 +1,54 @@
+// src/analytics/studio-usage.js
+import fs from "fs";
+import path from "path";
+var DAY_IN_MS = 24 * 60 * 60 * 1e3;
+var DEFAULT_DATABASE_PATH = ".eventcatalog/eventcatalog.db";
+var getStudioMode = (configFile) => {
+  const enabled = configFile.studio?.enabled;
+  if (enabled === false) return "off";
+  return configFile.output === "server" && enabled === true ? "server" : "dev";
+};
+var getStorageType = (configFile) => configFile.storage?.type || "memory";
+var loadSqlite = () => {
+  const emitWarning = process.emitWarning;
+  process.emitWarning = function(warning, ...args) {
+    const type = typeof args[0] === "object" ? args[0]?.type : args[0];
+    const message = typeof warning === "string" ? warning : warning?.message;
+    if (type === "ExperimentalWarning" && message?.startsWith("SQLite")) return;
+    return emitWarning.call(this, warning, ...args);
+  };
+  try {
+    return process.getBuiltinModule?.("node:sqlite");
+  } catch {
+    return void 0;
+  } finally {
+    process.emitWarning = emitWarning;
+  }
+};
+var UNKNOWN = "canvases:unknown";
+var serializeStudioUsage = (projectDirectory, configFile, now = Date.now()) => {
+  if (getStudioMode(configFile) === "off" || getStorageType(configFile) !== "sqlite") return UNKNOWN;
+  const file = path.resolve(projectDirectory, configFile.storage.path ?? DEFAULT_DATABASE_PATH);
+  if (!fs.existsSync(file)) return "canvases:0,changed7d:0,changed30d:0,deleted:0";
+  let database;
+  try {
+    const sqlite = loadSqlite();
+    if (!sqlite?.DatabaseSync) return UNKNOWN;
+    database = new sqlite.DatabaseSync(file, { readOnly: true });
+    const canvases = database.prepare(
+      "SELECT COUNT(*) AS total, SUM(updated_at >= ?) AS changed7d, SUM(updated_at >= ?) AS changed30d FROM studio_canvases"
+    ).get(now - 7 * DAY_IN_MS, now - 30 * DAY_IN_MS);
+    const { deleted } = database.prepare("SELECT COUNT(*) AS deleted FROM studio_deleted_canvases").get();
+    return `canvases:${canvases.total},changed7d:${canvases.changed7d ?? 0},changed30d:${canvases.changed30d ?? 0},deleted:${deleted}`;
+  } catch {
+    return UNKNOWN;
+  } finally {
+    database?.close();
+  }
+};
+
+export {
+  getStudioMode,
+  getStorageType,
+  serializeStudioUsage
+};

package/dist/{chunk-GAHKCOQM.js → chunk-JZN4RSMF.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-EUNQJO3J.js";
+} from "./chunk-RE7UTPWH.js";
 
 // src/utils/cli-logger.ts
 import pc from "picocolors";

package/dist/{chunk-JQMYHZWI.js → chunk-NEAVAFSJ.js}

@@ -1,22 +1,27 @@
 import {
-  raiseEvent
-} from "./chunk-4CFZUHGG.js";
+  getLicenseAnalytics
+} from "./chunk-AD7CL772.js";
 import {
   countResources,
   hashCatalogContent,
   serializeCounts
 } from "./chunk-ZAZHAVKB.js";
+import {
+  getStorageType,
+  getStudioMode,
+  serializeStudioUsage
+} from "./chunk-CA6WCQ2T.js";
+import {
+  raiseEvent
+} from "./chunk-NIVST4WY.js";
 import {
   TELEMETRY_REQUEST_TIMEOUT_MS,
   isTelemetryDisabled
 } from "./chunk-CPW6G62V.js";
-import {
-  getLicenseAnalytics
-} from "./chunk-AWOO63ME.js";
 import {
   getEventCatalogConfigFile,
   verifyRequiredFieldsAreInCatalogConfigFile
-} from "./chunk-RFIXKATC.js";
+} from "./chunk-4G7FSRPN.js";
 
 // src/analytics/log-build.js
 var isMCPEnabled = (configFile) => configFile.output === "server" && (configFile.mcp?.enabled ?? true);
@@ -31,7 +36,9 @@ var getFeatures = async (configFile) => {
     environments: Array.isArray(configFile.environments) && configFile.environments.length > 0,
     output: configFile.output || "static",
     mcp,
-    mcpAuth: mcp && (configFile.mcp?.auth?.enabled ?? false)
+    mcpAuth: mcp && (configFile.mcp?.auth?.enabled ?? false),
+    studio: getStudioMode(configFile),
+    storage: getStorageType(configFile)
   };
 };
 var getDirectoryProvider = (source) => {
@@ -132,7 +139,8 @@ var main = async (projectDir, { command = "build", license } = {}) => {
         generators: generatorNames.toString(),
         features: Object.keys(features).map((feature) => `${feature}:${features[feature]}`).join(","),
         directorySources: serializeDirectorySources(configFile),
-        resources: serializeCounts(resourceCounts)
+        resources: serializeCounts(resourceCounts),
+        studio: serializeStudioUsage(projectDir, configFile)
       },
       configFile
     );

package/dist/{chunk-4CFZUHGG.js → chunk-NIVST4WY.js}

@@ -4,7 +4,7 @@ import {
 } from "./chunk-CPW6G62V.js";
 import {
   VERSION
-} from "./chunk-EUNQJO3J.js";
+} from "./chunk-RE7UTPWH.js";
 
 // src/analytics/analytics.js
 import os from "os";

package/dist/{chunk-ENAG6UH7.js → chunk-NKNOXQ62.js}

@@ -1,6 +1,6 @@
 import {
   getEventCatalogConfigFile
-} from "./chunk-RFIXKATC.js";
+} from "./chunk-4G7FSRPN.js";
 
 // src/features.ts
 import { join } from "path";
@@ -13,10 +13,6 @@ var isOutputServer = async () => {
   const config = await getEventCatalogConfigFile(process.env.PROJECT_DIR || "");
   return config?.output === "server";
 };
-var isStudioEnabled = async () => {
-  const config = await getEventCatalogConfigFile(process.env.PROJECT_DIR || "");
-  return config?.output === "server" && config?.studio?.enabled === true;
-};
 var isIndexedSearchEnabled = async () => {
   const config = await getEventCatalogConfigFile(process.env.PROJECT_DIR || "");
   return config?.search?.type === "indexed";
@@ -30,7 +26,6 @@ var isAuthEnabled = async () => {
 export {
   getProjectOutDir,
   isOutputServer,
-  isStudioEnabled,
   isIndexedSearchEnabled,
   isAuthEnabled
 };

package/dist/{chunk-ZEY2XUJN.js → chunk-OX6TSVHY.js}

@@ -1,7 +1,3 @@
-import {
-  getFederationDiagnostics,
-  resolveFederationRules
-} from "./chunk-JJPB6EOZ.js";
 import {
   withFederationOutputTransaction
 } from "./chunk-WRNH5C3U.js";
@@ -10,13 +6,17 @@ import {
 } from "./chunk-5EPNFDT5.js";
 import {
   createFederationSourceProvider
-} from "./chunk-A2RZR3U4.js";
+} from "./chunk-6K7XZAYI.js";
 import {
   createFederationContentCache
 } from "./chunk-R7Z5ALYI.js";
+import {
+  getFederationDiagnostics,
+  resolveFederationRules
+} from "./chunk-JJPB6EOZ.js";
 import {
   getEventCatalogConfigFile
-} from "./chunk-RFIXKATC.js";
+} from "./chunk-4G7FSRPN.js";
 
 // src/federation/federate.ts
 import { createHash } from "crypto";

package/dist/{chunk-36RYTYT5.js → chunk-PD7KTSYN.js}

@@ -1,6 +1,6 @@
 import {
   getEventCatalogConfigFile
-} from "./chunk-RFIXKATC.js";
+} from "./chunk-4G7FSRPN.js";
 
 // src/resolve-catalog-dependencies.js
 import path from "path";

package/dist/{chunk-EUNQJO3J.js → chunk-RE7UTPWH.js}

@@ -1,5 +1,5 @@
 // package.json
-var version = "5.0.0-beta.9";
+var version = "5.0.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/chunk-S5GWAUG5.js

@@ -0,0 +1,29 @@
+// src/utils/child-process-signals.ts
+import { constants } from "os";
+var FORWARDED_SIGNALS = ["SIGINT", "SIGTERM", "SIGHUP"];
+var isRunning = (child) => child.exitCode === null && child.signalCode === null;
+var stopChildWithParent = (child, parent = process) => {
+  let received;
+  const onSignal = (signal) => {
+    received = signal;
+    if (isRunning(child)) child.kill(signal);
+  };
+  const onExit = () => {
+    if (isRunning(child)) child.kill("SIGTERM");
+  };
+  for (const signal of FORWARDED_SIGNALS) parent.on(signal, onSignal);
+  parent.on("exit", onExit);
+  return {
+    childClosed: () => {
+      for (const signal of FORWARDED_SIGNALS) parent.off(signal, onSignal);
+      parent.off("exit", onExit);
+      if (!received) return false;
+      parent.exit(128 + constants.signals[received]);
+      return true;
+    }
+  };
+};
+
+export {
+  stopChildWithParent
+};

package/dist/{chunk-TZVDMWQX.js → chunk-YQGRMDRB.js}

@@ -1,10 +1,10 @@
 import {
   logger
-} from "./chunk-GAHKCOQM.js";
+} from "./chunk-JZN4RSMF.js";
 import {
   cleanup,
   getEventCatalogConfigFile
-} from "./chunk-RFIXKATC.js";
+} from "./chunk-4G7FSRPN.js";
 
 // src/generate.js
 import path from "path";
@@ -54,10 +54,12 @@ var generate = async (PROJECT_DIRECTORY) => {
       for (const { plugin } of errors) {
         logger.error(`  - ${plugin}`, "generator");
       }
+      process.exitCode = 1;
     }
   } catch (error) {
     console.error(error);
     await cleanup(PROJECT_DIRECTORY);
+    process.exitCode = 1;
   }
 };
 

package/dist/constants.cjs

@@ -25,7 +25,7 @@ __export(constants_exports, {
 module.exports = __toCommonJS(constants_exports);
 
 // package.json
-var version = "5.0.0-beta.9";
+var version = "5.0.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.js

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-EUNQJO3J.js";
+} from "./chunk-RE7UTPWH.js";
 export {
   VERSION
 };

package/dist/docs/api/02-config.md

@@ -339,7 +339,7 @@ module.exports = {
 
 ### `navigation` {#navigation}
 
-<AddedIn version="4.0" />
+<AddedIn version="4.0.0" />
 
 - Type: `object`
 
@@ -587,7 +587,7 @@ docs: {
 Configuration for [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant).
 
 :::info
-The `chat` property requires a Scale plan and `output: 'server'` to take effect.
+The `chat` property requires `output: 'server'` to take effect.
 :::
 
 ```js title="eventcatalog.config.js"
@@ -608,7 +608,7 @@ module.exports = {
 
 Configuration for the built-in EventCatalog MCP server.
 
-The MCP server requires a Scale plan and `output: 'server'`. When those prerequisites are met, it is enabled by default. Set
+The MCP server requires `output: 'server'`. When that prerequisite is met, it is enabled by default. Set
 `mcp.enabled` to `false` to prevent the MCP routes from being registered and hide the MCP connection actions on domain and
 system pages.
 
@@ -623,14 +623,62 @@ module.exports = {
 
 | Property | Type | Default | Description |
 |---|---|---|---|
-| `mcp.enabled` | `boolean` | `true` | Enables or disables the built-in MCP server when its SSR and Scale prerequisites are met. |
+| `mcp.enabled` | `boolean` | `true` | Enables or disables the built-in MCP server when its SSR prerequisite is met. |
 
 See the [MCP server guide](/docs/development/ask-your-architecture/mcp-server/getting-started) for scoped domain and system
 endpoints, client setup, and OAuth configuration.
 
+### `studio` {#studio}
+
+<AddedIn version="5.0.0" />
+
+- Type: `object`
+
+Configuration for [EventCatalog Studio](/docs/development/studio/introduction), the collaborative canvases at `/studio`.
+
+Studio is on in `eventcatalog dev`. In production it needs `output: 'server'` and `studio.enabled: true`. Set
+`studio.enabled` to `false` to turn it off everywhere.
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  output: 'server',
+  studio: {
+    enabled: true,
+  },
+};
+```
+
+| Option | Type | Default | Description |
+| ------ | ---- | ------- | ----------- |
+| `studio.enabled` | `boolean` | `false` | Turns Studio on in production (`output: 'server'`, served with `eventcatalog start`). Studio is on in `eventcatalog dev` unless this is `false`. |
+
+See [Run Studio in production](/docs/development/studio/run-studio-in-production) and the [Studio configuration reference](/docs/development/studio/reference#configuration).
+
+### `storage` {#storage}
+
+<AddedIn version="5.0.0" />
+
+- Type: `object`
+
+Where EventCatalog keeps state between restarts, such as Studio's canvases.
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  storage: {
+    type: 'sqlite',
+    path: '.eventcatalog/eventcatalog.db',
+  },
+};
+```
+
+| Option | Type | Default | Description |
+| ------ | ---- | ------- | ----------- |
+| `storage.type` | `'memory'` \| `'sqlite'` | `'memory'` | `'memory'` keeps state while the server runs. `'sqlite'` keeps it in a database file. SQLite needs Node.js 22.13 or later. |
+| `storage.path` | `string` | `'.eventcatalog/eventcatalog.db'` | The database file, relative to your catalog. In a container, put it on a volume so it survives redeploys. |
+
 ### `search` {#search}
 
-<AddedIn version="3.36.0" />
+<AddedIn version="3.36.1" />
 
 - Type: `object`
 
@@ -688,11 +736,13 @@ module.exports = {
 - Type: `string`
 
 :::tip
-For Scale plans. This gives you the ability to show your own GitHub repository in EventCatalog (in the header bar).
+This gives you the ability to show your own GitHub repository in EventCatalog (in the header bar).
 :::
 
 URL to your repository for EventCatalog.
 
+When set, the header shows a link to your repository next to the EventCatalog Discord and GitHub links. The EventCatalog links are always shown.
+
 ```js title="eventcatalog.config.js"
 module.exports = {
   repositoryUrl: 'https://github.com/boyney123/eventcatalog-demo',
@@ -962,7 +1012,7 @@ See the [Customize tables](/docs/development/customization/customize-tables) doc
 
 ### `systems` {#systems}
 
-<AddedIn version="4.0" />
+<AddedIn version="4.0.0" />
 
 - Type: `object`
 

package/dist/docs/development/00-why-eventcatalog.md

@@ -5,10 +5,10 @@ keywords:
 - EventCatalog introduction
 sidebar_label: Why EventCatalog?
 title: Why EventCatalog?
-description: EventCatalog is an open source project to help you bring discoverability to your event-driven architecture.
+description: EventCatalog helps you bring discoverability to your event-driven architecture.
 ---
 
-Software architecture consists of many different primitives including domains, systems, services, APIS, contracts, messages and many more.
+Software architecture consists of many different primitives including [domains](/docs/development/guides/domains/introduction), [systems](/docs/development/guides/systems/introduction), [services](/docs/development/guides/resources/services/introduction), [APIs](/docs/development/guides/resources/schemas/add-specifications-to-services/add-openapi-specifications), [contracts](/docs/development/guides/resources/schemas/what-are-schemas-and-specifications), [messages](/docs/development/guides/resources/messages/what-are-messages) and many more.
 
 As systems grow, complexity grows. Documentation becomes important for teams but teams struggle to keep docs in sync, or relevant to what they are trying to model.
 
@@ -18,11 +18,11 @@ As systems grow, complexity grows. Documentation becomes important for teams but
 
 ### What is EventCatalog?
 
-EventCatalog is an open source documentation tool that is built for software architecture.
+EventCatalog is a tool that is built for software architecture.
 
 We focus on architecture primitives like domains, systems and resources (e.g services, messages) and let you document your architecture with primitives you are already familiar with. 
 
-EventCatalog creates an internal architecture graph of how your systems work. This makes EventCatalog accessible to your AI agents, LLMs and AI workflows and [creates context of your business and architecture](/docs/development/ask-your-architecture/intro).
+EventCatalog creates an internal [architecture graph](/docs/development/guides/architecture-graph) of how your systems work. This makes EventCatalog accessible to your AI agents, LLMs and AI workflows and [creates context of your business and architecture](/docs/development/ask-your-architecture/intro).
 
 EventCatalog is technology agnostic, this means you can document and model any systems you have.
 
@@ -34,20 +34,20 @@ EventCatalog is technology agnostic, this means you can document and model any s
   - Document high level information for stakeholders while providing lower level details to your teams.
   - Connect to your AI Agents and AI Workflows. Give your LLMs the context they need.
 - **Create a documentation solution you can trust**
-  - Sync documentation from your code with our Agent
-  - Automate documentation from your OpenAPI, AsyncAPI, or schema registries
+  - Sync documentation from your code with the [EventCatalog Agent](/docs/development/ask-your-architecture/agents/code-to-docs)
+  - Automate documentation from your [OpenAPI](/integrations/openapi), [AsyncAPI](/integrations/asyncapi), or [schema registries](/integrations)
   - Use EventCatalog Agent to sync code to docs from your CI/CD workflows.
   - Write your own automation and plugins with the [EventCatalog SDK](/docs/sdk)
 - **Help you detect breaking changes before they reach production**
-  - Use EventCatalog Agent to detect breaking schema changes
+  - Use EventCatalog Agent to [detect breaking schema changes](/docs/development/ask-your-architecture/agents/breaking-changes)
   - Bring your own model and get notified when things break
-- **Use natural langugage to query your architecture**
+- **Use natural language to query your architecture**
   - Connect AI tools to your architecture using [EventCatalog's MCP server](/docs/development/ask-your-architecture/mcp-server/introduction)
-  - Ask architectural questions grounded in your documented domains, services, events, data products, and schemas
+  - Ask architectural questions grounded in your documented domains, services, events, [data products](/docs/development/guides/resources/data-products/introduction), and schemas
 - **Help your teams understand the bigger picture**
   - Help business stakeholders understand the bigger picture
-  - Visualize your architecture and future ideas
-  - Document key business workflows
+  - Visualize your architecture, and design future ideas with [EventCatalog Studio](/docs/development/studio/introduction)
+  - Document key business workflows as [flows](/docs/development/guides/resources/flows/introduction)
 
 **EventCatalog is self-hosted. You own your data and host it wherever you want.**
 

package/dist/docs/development/01-fundamentals.md

@@ -8,17 +8,20 @@ title: Fundamentals
 description: Understanding the fundamentals of EventCatalog
 ---
 
-EventCatalog is a self hosted [open source documentation tool](https://github.com/event-catalog/eventcatalog/stargazers) for software architecture. It allows you to document your architecture using software primitives and patterns such as domains, systems and resources rather than random documentation pages (e.g Confluence).
+import CatalogModel from '@site/src/components/CatalogModel';
+import DiagramLevels from '@site/src/components/DiagramLevels';
+
+EventCatalog is a self-hosted tool to document, visualize and collaborate on your software architecture. You document it using software primitives and patterns such as [domains](/docs/development/guides/domains/introduction), [systems](/docs/development/guides/systems/introduction) and [resources](/docs/resources), rather than scattered documentation pages (e.g. Confluence).
 
 EventCatalog follows the [docs-as-code](https://www.writethedocs.org/guide/docs-as-code/) pattern. Your documentation is stored in code using [markdown (MDX)](https://mdxjs.com/) and stays private, in your own repository and infrastructure. 
 
 At its core, EventCatalog gives you a small set of building blocks for your documentation.
 
-![EventCatalog model showing domains, systems, resources, contracts, and ownership](./img/levels-catalog.png)
+<CatalogModel />
 
-- **Domains (Level 1)** - a domain describes a business boundary
-- **Systems (Level 2)** - a system is a collection of resources that work together to perform a function.
-- **Resources (Level 3)** - individual resources (e.g services, messages, data stores) that can be assigned to systems or domains.
+- **Domains** - a domain describes a business boundary.
+- **Systems** - a system is a collection of resources that work together to perform a function.
+- **Resources** - individual resources (e.g. services, messages, data stores) that can be assigned to systems or domains.
 
 :::info What blocks to use?
 All building blocks are optional in your catalog. It's up to you how you want to model your documentation.
@@ -49,19 +52,23 @@ Teams and users can own domains, systems, resources, and contracts. This makes o
 
 ## Levels of detail
 
-Architecture documentation all have different audiences, and EventCatalog can be useful to anyone in your organization.
+Architecture documentation has different audiences, and EventCatalog can be useful to anyone in your organization. Stakeholders want the big picture, and developers want the implementation details.
+
+Every diagram in EventCatalog has three levels of detail, **L1**, **L2** and **L3**, and they mean the same thing on every diagram:
+
+| Level | What you see | What it answers | Example |
+|-------|--------------|-----------------|---------|
+| **L1** | Domains, systems and the relationships between them | Which business boundaries and systems exist, and how do they depend on each other? | `Shopping` domain, `Cart System` |
+| **L2** | The services and data stores inside them, and how they connect | What runs inside a system, and what does it talk to? | `Cart API`, cart database |
+| **L3** | Everything in L2, plus the messages and channels | What flows between services? | `CartUpdated` event, `cart.events` topic |
 
-You can define a high level of information for stakeholders whilst whilst giving lower level implementation details for developers.
+<DiagramLevels />
 
-| Level | Name | What it answers | Example |
-|-------|------|-----------------|---------|
-| Level 1 | Domains | High level, what business boundary are we looking at? | Shopping |
-| Level 2 | Systems | What software capability exists inside that boundary? | Cart System |
-| Level 3 | Resources | What makes up, connects to, or documents that system? | Cart API, cart database, checkout flow |
+When a level doesn't apply to a diagram, it's greyed out. On a service diagram, for example, L1 is greyed out because there are no domains or systems to show above it. Read more in the [domain diagram](/docs/development/guides/domains/visualize-domains/domain-diagram) and [system diagram](/docs/development/guides/systems/system-context-maps) docs.
 
 Contracts and ownership sit across these levels. A service can implement an OpenAPI contract. A message can have a schema. A team can own a domain, system, or resource.
 
-This gives different users a way into the same catalog. Architects can start at domains, platform teams can reason about systems, and developers can drill into the resources and contracts they work with every day.
+This gives different users a way into the same catalog. Architects can start at L1, platform teams can explore the services and data stores in L2, and developers can drill into the messages and contracts they work with every day in L3.
 
 ## Docs-as-code
 

package/dist/docs/development/01-getting-started/configuration-overview.md

@@ -15,12 +15,12 @@ Configuration lives in `eventcatalog.config.js` at the root of your project. You
 
 ## Configuring environment variables {#configuring-environment-variables}
 
-Some features need values that should not live directly in `eventcatalog.config.js`, such as license keys or provider credentials.
+Some features need values that should not live directly in `eventcatalog.config.js`, such as API keys or provider credentials.
 
 Put those values in a `.env` file in the root of your catalog. EventCatalog loads `.env` when it runs locally and when it builds.
 
 ```bash title=".env (example)"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-api-key
+OPENAI_API_KEY=your-api-key
 ```
 
 Do not commit real secrets to source control.

package/dist/docs/development/01-getting-started/installation.md

@@ -54,6 +54,14 @@ npm run dev
 
 Open [http://localhost:3000](http://localhost:3000) to view your catalog.
 
+:::info Licensing
+EventCatalog v5 is source-available under the [Business Source License](/license). It's free in production for individuals, open-source projects, teaching and research, and organisations under $10M in revenue and under $10M raised. Larger organisations get a 60-day evaluation, then need a [commercial license](/pricing).
+
+The "Trial" countdown you see in the header is a reminder. Trying EventCatalog with sample content, like the catalog this command creates, is always free and doesn't start your evaluation. That starts when your catalog documents real systems that people rely on. Your builds never stop working when a trial or license ends.
+
+[Licensing FAQ](/license-faq) · [Add your license file](/docs/development/license/license-file)
+:::
+
 ## CLI installation flags
 
 You can pass flags to `create-eventcatalog` to customize the catalog that gets created.
@@ -92,7 +100,7 @@ Then ask your AI agent to inspect your codebase and generate EventCatalog docume
 Look at my directory and generate EventCatalog documentation from information you find.
 ```
 
-The generated files can be edited like any other EventCatalog documentation. Learn more about [EventCatalog skills](/docs/development/ask-your-architecture/skills/introduction).
+The generated files can be edited like any other EventCatalog documentation. Learn more about [EventCatalog skills](/docs/development/ask-your-architecture/install-skills).
 
 ## Optional: Use EventCatalog Editor
 

package/dist/docs/development/_getting-started.mdx

@@ -4,7 +4,7 @@ keywords:
 - EventCatalog introduction
 sidebar_label: Getting Started
 title: Getting Started
-description: EventCatalog is an open source project to help you bring discoverability to your event-driven architecture.
+description: EventCatalog helps you bring discoverability to your event-driven architecture.
 hide_title: true
 hide_table_of_contents: true
 hide_breadcrumbs: true

package/dist/docs/development/ask-your-architecture/01-intro.md

@@ -11,11 +11,11 @@ import AddedIn from '@site/src/components/MDX/AddedIn';
 
 EventCatalog creates an internal graph of your architecture. Perfect for AI and LLMs.
 
-EventCatalog supports five ways to use AI with your catalog:
+EventCatalog supports six ways to use AI with your catalog:
 
-- [llms.txt](/docs/development/ask-your-architecture/llms.txt) - Give AI tools a machine-readable index of your catalog.
-- [schemas.txt](/docs/development/ask-your-architecture/schemas.txt) - Give AI tools access to your schemas and specifications.
-- [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant) - AI Chat in your Catalog.
 - [EventCatalog MCP Server](/docs/development/ask-your-architecture/mcp-server/introduction) - Connect EventCatalog to Agents through MCP
+- [AI Skills](/docs/development/ask-your-architecture/install-skills) - Install our Skills to help you manage your catalog
 - [EventCatalog Agent](/docs/development/ask-your-architecture/agents/overview) - CI/CD Agent for breaking changes and doc updates
-- [AI Skills](/docs/development/ask-your-architecture/skills/introduction) - Install our Skills to help you manage your catalog
+- [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant) - AI Chat in your Catalog.
+- [llms.txt](/docs/development/ask-your-architecture/llms.txt) - Give AI tools a machine-readable index of your catalog.
+- [schemas.txt](/docs/development/ask-your-architecture/schemas.txt) - Give AI tools access to your schemas and specifications.

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/01-what-is-eventcatalog-assistant.md

@@ -9,10 +9,6 @@ description: Learn how EventCatalog Assistant helps users explore documentation
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 EventCatalog Assistant brings AI chat to your catalog.
 
 It is embedded directly into your documentation site, enabling users to quickly find answers, understand your system, and succeed without manually searching through pages.

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/02-configuration.md

@@ -8,9 +8,6 @@ description: Configure EventCatalog Assistant
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
 
 **EventCatalog Assistant is shown by default.**
 
@@ -82,3 +79,18 @@ export const configuration = {
 ```
 
 Once you have configured your model, restart EventCatalog and you can start asking questions about your architecture.
+
+### Troubleshooting
+
+#### `eventcatalog.chat.js` fails to load
+
+<AddedIn version="5.0.0" />
+
+If your catalog has an `eventcatalog.chat.js` file but it fails to load (for example, a package it imports isn't installed),
+the assistant explains the problem instead of answering:
+
+- **In `eventcatalog dev`**, the assistant shows why the file didn't load and the steps to fix it: install the packages your
+  `eventcatalog.chat.js` imports (for example `npm install ai @ai-sdk/anthropic`), add the provider's API key to your `.env`
+  file, and restart EventCatalog.
+- **Everywhere else**, the reason is not shown to readers. The assistant tells them that the catalog owner can find the cause
+  in the server logs, under `Error loading chat configuration`.

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/03-bring-your-own-tools.md

@@ -11,11 +11,8 @@ title: Custom Tools
 description: Extend EventCatalog Assistant with custom tools to bring real-time data, metrics, and integrations into your architecture conversations
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-<PlanBanner plan="Scale" />
-
 EventCatalog Assistant comes with built-in tools that allow the AI to search and understand your architecture documentation. But what if you could go beyond static documentation and bring **real-time data** directly into your conversations?
 
 With custom tools, you can extend the assistant to query your production metrics, check service health, look up on-call engineers, fetch data from your databases, and much more.

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "EventCatalog Assistant",
-  "position": 4,
+  "position": 5,
   "collapsible": true,
   "collapsed": true,
   "link": {

package/dist/docs/development/ask-your-architecture/02-llms.txt.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 6
 keywords:
 - llms.txt
 - AI