@eventcatalog/core 5.0.0-beta.8 → 5.0.0

package/eventcatalog/src/utils/node-graphs/domain-levels-node-graph.ts

@@ -267,7 +267,7 @@ export const buildDomainGraph = ({
         draggable: false,
         selectable: false,
         data: {
-          domain: { name: d.data.name, version: d.data.version },
+          domain: { id: d.data.id, name: d.data.name, version: d.data.version },
           // The domain viewed may itself be a subdomain of another
           subdomain: !!parentId || parentDomainOf.has(d.data.id),
           isFocused: !parentId,
@@ -309,7 +309,7 @@ export const buildDomainGraph = ({
         position: { x: 0, y: 0 },
         ...(parentId ? { parentId } : {}),
         data: {
-          domain: { name: other.data.name, version: other.data.version },
+          domain: { id: other.data.id, name: other.data.name, version: other.data.version },
           subdomain: !!parentId,
           isFocused: false,
           otherDomain: true,
@@ -375,7 +375,7 @@ export const buildDomainGraph = ({
         type: 'system-group',
         parentId: domainGroup,
         position: { x: 0, y: 0 },
-        data: { system: { name: system.data.name, version: system.data.version } },
+        data: { system: { id: system.data.id, name: system.data.name, version: system.data.version } },
       });
     }
     addNodes(graph.nodes);

package/eventcatalog/src/utils/node-graphs/field-node-graph.ts

@@ -1,6 +1,6 @@
 import type { Node, Edge } from '@xyflow/react';
 import { createEdge, createNode, buildContextMenuForMessage, buildContextMenuForService } from './utils/utils';
-import { layoutNodeGraph } from '@utils/node-graphs/layout-node-graph';
+import { layoutWithElk } from '@eventcatalog/visualiser/layout';
 
 export interface FieldOccurrence {
   messageId: string;
@@ -173,5 +173,7 @@ export const getNodesAndEdges = async ({
 
   if (!layout) return { nodes, edges };
 
-  return layoutNodeGraph({ nodes, edges });
+  // Lays out with ELK directly rather than layoutNodeGraph: this runs in the browser (the Fields Explorer),
+  // and layoutNodeGraph's cache reads the catalog's config, which would put the config in the browser's bundle
+  return (await layoutWithElk({ nodes, edges })) as unknown as { nodes: Node[]; edges: Edge[] };
 };

package/eventcatalog/src/utils/node-graphs/layout-node-graph.ts

@@ -1,7 +1,14 @@
 import { hideMessageNodes, layoutWithElk } from '@eventcatalog/visualiser/layout';
+import { isSSR } from '@utils/feature';
 
 type Graph = { nodes: any[]; edges: any[] };
 
+// A build renders one route at a time (every message's docs page, then every schema page), so the
+// cache has to outlast a whole route to be reused. A server keeps running as the catalog changes and
+// renders pages as they're asked for, so it keeps the most recent layouts only.
+const MAX_CACHED_LAYOUTS = isSSR() ? 200 : 5000;
+const layouts = new Map<string, ReturnType<typeof layoutWithElk>>();
+
 /**
  * Lays a node graph out for the visualiser (with ELK, left to right). Builders
  * create their nodes and edges without positions and lay the finished graph
@@ -9,7 +16,19 @@ type Graph = { nodes: any[]; edges: any[] };
  * (nodes with children) are sized to fit them, and edges get the route they're
  * drawn along (`data.route`), with room for their labels.
  */
-export const layoutNodeGraph = async <G extends Graph>(graph: G): Promise<G> => (await layoutWithElk(graph)) as unknown as G;
+export const layoutNodeGraph = async <G extends Graph>(graph: G): Promise<G> => {
+  // A build lays the same graph out on several pages (a message's docs, visualiser and schema pages):
+  // reuse the layout. Each caller gets its own copy, so it can't change the one kept.
+  const key = JSON.stringify(graph);
+  let layout = layouts.get(key);
+  if (!layout) {
+    layout = layoutWithElk(graph);
+    layouts.set(key, layout);
+    layout.catch(() => layouts.delete(key));
+    if (layouts.size > MAX_CACHED_LAYOUTS) layouts.delete(layouts.keys().next().value!);
+  }
+  return structuredClone(await layout) as unknown as G;
+};
 
 /**
  * Lays out the graphs of a levels page: level 1 (`overview`: domains, systems

package/eventcatalog/src/utils/node-graphs/node-resource.ts

@@ -0,0 +1,67 @@
+/**
+ * The catalog resource a diagram node shows, for the node types the node graphs build. Has no imports so it can
+ * be shared by the server and the browser (the visualiser's "Open in Studio", the MCP App views).
+ */
+
+// The collection each node type shows a resource of
+const NODE_COLLECTIONS: Record<string, string> = {
+  service: 'services',
+  services: 'services',
+  agent: 'agents',
+  agents: 'agents',
+  event: 'events',
+  events: 'events',
+  command: 'commands',
+  commands: 'commands',
+  query: 'queries',
+  queries: 'queries',
+  channel: 'channels',
+  channels: 'channels',
+  flow: 'flows',
+  flows: 'flows',
+  data: 'containers',
+  containers: 'containers',
+  'data-products': 'data-products',
+  domain: 'domains',
+  domains: 'domains',
+  'context-domain': 'domains',
+  'domain-group': 'domains',
+  system: 'systems',
+  systems: 'systems',
+  'system-group': 'systems',
+};
+
+// Where each node type keeps the resource it shows
+const RESOURCE_DATA_KEYS = [
+  'service',
+  'agent',
+  'message',
+  'channel',
+  'data',
+  'dataProduct',
+  'flow',
+  'entity',
+  'domain',
+  'system',
+  'custom',
+];
+
+type DiagramNode = { type?: string; data?: Record<string, unknown> };
+type ResourceDetails = { id?: unknown; version?: unknown; [key: string]: unknown };
+
+/** The resource a node shows, as in its data: the fields shown, or the catalog entry's data (if it holds the entry) */
+export const getNodeResourceDetails = (node: DiagramNode): ResourceDetails | undefined => {
+  const data = node.data ?? {};
+  const resource = RESOURCE_DATA_KEYS.map((key) => data[key]).find(Boolean) as
+    | (ResourceDetails & { data?: ResourceDetails })
+    | undefined;
+  return resource?.data ?? resource;
+};
+
+/** The catalog resource a node shows (its collection, id and version), if it shows one */
+export const getNodeCatalogResource = (node: DiagramNode): { collection: string; id: string; version?: string } | undefined => {
+  const collection = NODE_COLLECTIONS[node.type ?? ''];
+  const details = getNodeResourceDetails(node);
+  if (!collection || typeof details?.id !== 'string') return undefined;
+  return { collection, id: details.id, ...(typeof details.version === 'string' && { version: details.version }) };
+};

package/eventcatalog/src/utils/node-graphs/systems-node-graph.ts

@@ -142,7 +142,7 @@ const wrapNodesInSystemGroup = (systemNodes: any[], system: any) => {
     draggable: false,
     selectable: false,
     data: {
-      system: { name: system.data.name, version: system.data.version },
+      system: { id: system.data.id, name: system.data.name, version: system.data.version },
       // The system is the resource being viewed on its own diagram
       isFocused: true,
     },

package/eventcatalog/src/utils/page-loaders/hybrid-page.ts

@@ -24,7 +24,9 @@ export class HybridPage<T = any> {
   }
 
   /**
-   * Static method for getting data
+   * The page's data: its props in a static build, or looked up from its URL on a server. Undefined
+   * when nothing matches (an unknown resource or version): the page then returns
+   * `Astro.rewrite('/404')`. Throwing a Response instead made Astro answer with an empty 500.
    */
   static async getData(astro: AstroGlobal): Promise<any> {
     // Try props first (static mode)
@@ -32,13 +34,7 @@ export class HybridPage<T = any> {
       return this.transformProps(astro.props);
     }
 
-    const data = await this.fetchData(astro.params);
-
-    if (!data) {
-      throw this.createNotFoundResponse();
-    }
-
-    return data;
+    return (await this.fetchData(astro.params)) ?? undefined;
   }
 
   /**
@@ -58,11 +54,4 @@ export class HybridPage<T = any> {
   protected static transformProps(props: any): any {
     return props;
   }
-
-  protected static createNotFoundResponse(): Response {
-    return new Response(null, {
-      status: 404,
-      statusText: 'Not found',
-    });
-  }
 }

package/eventcatalog/src/utils/page-title.ts

@@ -0,0 +1,15 @@
+import config from '@config';
+
+/** The catalog's name: `title` in eventcatalog.config.js, or EventCatalog when it has none */
+export const getCatalogTitle = (): string => config?.title?.trim() || 'EventCatalog';
+
+/**
+ * A page's title, as browser tabs and link previews show it: the page's own title, then the
+ * catalog's (`Domains | Ordering | Acme Inc`), so tabs show the page first. A page without a title
+ * of its own (the homepage) is just the catalog's.
+ */
+export const formatPageTitle = (title?: string): string => {
+  const catalogTitle = getCatalogTitle();
+  const pageTitle = title?.trim();
+  return pageTitle && pageTitle !== catalogTitle ? `${pageTitle} | ${catalogTitle}` : catalogTitle;
+};

package/eventcatalog/src/utils/syntax-highlighter-renderer.ts

@@ -0,0 +1,64 @@
+import { createElement, type CSSProperties, type ReactNode } from 'react';
+import { createStyleObject } from 'react-syntax-highlighter/dist/cjs/create-element.js';
+
+type Stylesheet = { [selector: string]: CSSProperties };
+type HighlightedNode = {
+  type: 'element' | 'text';
+  value?: string | number;
+  tagName?: any;
+  properties?: { className?: string[]; style?: CSSProperties; [key: string]: unknown };
+  children?: HighlightedNode[];
+};
+
+const selectorsByStylesheet = new WeakMap<Stylesheet, Set<string>>();
+
+/** The class names a theme styles, worked out once per theme */
+const stylesheetSelectors = (stylesheet: Stylesheet) => {
+  let selectors = selectorsByStylesheet.get(stylesheet);
+  if (!selectors) {
+    selectors = new Set(Object.keys(stylesheet).flatMap((selector) => selector.split('.')));
+    selectorsByStylesheet.set(stylesheet, selectors);
+  }
+  return selectors;
+};
+
+const renderNode = (node: HighlightedNode, stylesheet: Stylesheet, useInlineStyles: boolean, key: string): ReactNode => {
+  if (node.type === 'text') return node.value;
+  if (!node.tagName) return undefined;
+
+  const properties = node.properties ?? {};
+  const classNames = properties.className;
+  let props;
+  if (!useInlineStyles) {
+    props = { ...properties, className: classNames?.join(' ') };
+  } else {
+    // Theme classes become inline styles; any other class names stay
+    const selectors = stylesheetSelectors(stylesheet);
+    const className =
+      classNames && (classNames.includes('token') ? ['token'] : []).concat(classNames.filter((name) => !selectors.has(name)));
+    props = {
+      ...properties,
+      className: className?.join(' ') || undefined,
+      style: createStyleObject(classNames ?? [], { ...properties.style }, stylesheet),
+    };
+  }
+
+  const children = (node.children ?? []).map((child, i) => renderNode(child, stylesheet, useInlineStyles, `code-segment-1-${i}`));
+  return createElement(node.tagName, { key, ...props }, children);
+};
+
+/**
+ * Renders react-syntax-highlighter's rows as its default renderer does (same elements, styles and keys), but
+ * works out the theme's class names once per theme rather than for every token: the default renderer did
+ * that for every token, which made highlighting a schema on the server take tens of milliseconds a page.
+ * Set `wrapLines`: with a custom renderer, react-syntax-highlighter turns it on when it isn't set.
+ */
+export const renderHighlightedRows = ({
+  rows,
+  stylesheet,
+  useInlineStyles,
+}: {
+  rows: HighlightedNode[];
+  stylesheet: Stylesheet;
+  useInlineStyles: boolean;
+}): ReactNode[] => rows.map((node, i) => renderNode(node, stylesheet, useInlineStyles, `code-segment-${i}`));

package/eventcatalog/src/utils/trial.ts

@@ -5,6 +5,19 @@ export const LICENSE_FAQ_URL = 'https://www.eventcatalog.dev/license-faq';
 // Where a commercial license is renewed
 export const LICENSE_RENEW_URL = 'https://eventcatalog.cloud';
 
+// Where the Business plan is bought: the order form on the website
+export const BUY_BUSINESS_URL = 'https://www.eventcatalog.dev/buy?source=cli';
+
+// Prices for a commercial license, linked while the trial is running
+export const PRICING_URL = 'https://www.eventcatalog.dev/pricing';
+
+// Questions about licensing or buying: talk to the EventCatalog team
+export const TALK_TO_US_URL = 'https://www.eventcatalog.dev/book-demo';
+
+// Shown with the trial, so organisations that qualify for Free Use don't read it as "EventCatalog is now paid"
+export const FREE_USE_NOTE =
+  'Under $10M revenue and $10M raised, an individual or an open-source project? You qualify for Free Use; get a free key at eventcatalog.cloud.';
+
 const DAY_IN_MS = 24 * 60 * 60 * 1000;
 
 export type TrialStatus = {

package/package.json

@@ -7,7 +7,7 @@
   },
   "license": "BUSL-1.1",
   "type": "module",
-  "version": "5.0.0-beta.8",
+  "version": "5.0.0",
   "publishConfig": {
     "access": "public"
   },
@@ -47,10 +47,10 @@
   ],
   "dependencies": {
     "@ai-sdk/react": "^4.0.109",
-    "@astrojs/markdown-remark": "^7.3.1",
-    "@astrojs/mdx": "^8.0.1",
-    "@astrojs/node": "^11.1.6",
-    "@astrojs/react": "^6.0.6",
+    "@astrojs/markdown-remark": "^7.3.2",
+    "@astrojs/mdx": "^8.0.3",
+    "@astrojs/node": "^11.1.7",
+    "@astrojs/react": "^7.0.1",
     "@astrojs/rss": "^4.0.19",
     "@asyncapi/avro-schema-parser": "3.0.24",
     "@asyncapi/parser": "^3.6.0",
@@ -63,7 +63,6 @@
     "@hocuspocus/provider": "^4.7.0",
     "@hocuspocus/server": "^4.7.0",
     "@iconify-json/logos": "^1.2.4",
-    "@mcp-b/webmcp-local-relay": "5.1.0",
     "@mcp-b/webmcp-polyfill": "5.1.0",
     "@mermaid-js/layout-elk": "^0.2.0",
     "@modelcontextprotocol/ext-apps": "^1.7.5",
@@ -81,7 +80,7 @@
     "@tanstack/react-table": "^8.17.3",
     "@xyflow/react": "^12.12.0",
     "ai": "^7.0.106",
-    "astro": "7.3.3",
+    "astro": "7.3.8",
     "astro-expressive-code": "^0.44.0",
     "astro-seo": "^1.2.0",
     "boxen": "^8.0.1",
@@ -99,6 +98,7 @@
     "gray-matter": "^4.0.3",
     "hono": "^4.13.7",
     "html-to-image": "^1.11.11",
+    "htmlparser2": "^12.0.0",
     "js-yaml": "^4.3.2",
     "jsonpath-plus": "^10.4.0",
     "jsonwebtoken": "^9.0.2",
@@ -139,10 +139,10 @@
     "uuid": "^11.1.1",
     "y-protocols": "^1.0.7",
     "yjs": "^13.6.33",
-    "zod": "^4.3.6",
-    "@eventcatalog/sdk": "2.30.0-beta.1",
-    "@eventcatalog/visualiser": "^5.0.0-beta.4",
-    "@eventcatalog/linter": "1.2.0-beta.2"
+    "zod": "^4.6.6",
+    "@eventcatalog/linter": "1.2.0",
+    "@eventcatalog/sdk": "2.30.0",
+    "@eventcatalog/visualiser": "^5.0.0"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",

package/dist/docs/development/ask-your-architecture/05-skills/02-installation.md

@@ -1,60 +0,0 @@
----
-sidebar_position: 2
-keywords:
-- AI Skills
-- installation
-sidebar_label: Installation
-title: Installing AI Skills
-description: How to install EventCatalog AI skills for your AI coding agent
----
-
-## CLI install (recommended)
-
-Use [npx skills](https://github.com/vercel-labs/skills) to install skills directly into your project:
-
-```bash
-# Install all EventCatalog skills
-npx skills add event-catalog/skills
-
-# Install a specific skill
-npx skills add event-catalog/skills --skill catalog-documentation-creator
-```
-
-This copies the skill files into your project's `.claude/skills/` directory where your AI agent can access them.
-
-## Clone and copy
-
-Clone the repository and copy the skills you need:
-
-```bash
-git clone https://github.com/event-catalog/skills.git
-cp -r skills/skills/catalog-documentation-creator .claude/skills/
-```
-
-## Git submodule
-
-Add as a submodule for easy updates:
-
-```bash
-git submodule add https://github.com/event-catalog/skills.git .claude/skills/eventcatalog
-```
-
-When new skills are released, pull updates with:
-
-```bash
-git submodule update --remote
-```
-
-## Fork and customize
-
-Fork the repository and tailor skills to your team's conventions:
-
-1. Fork [event-catalog/skills](https://github.com/event-catalog/skills) on GitHub
-2. Modify skills to match your naming conventions, ownership patterns, and schema formats
-3. Install from your fork:
-
-```bash
-npx add-skill https://github.com/YOUR_ORG/eventcatalog-skills
-```
-
-This is useful when your team has specific conventions for IDs, owners, or folder structures that differ from the defaults.

package/dist/docs/development/ask-your-architecture/05-skills/_category_.json

@@ -1,11 +0,0 @@
-{
-  "label": "Skills",
-  "position": 7,
-  "collapsible": true,
-  "collapsed": true,
-  "link": {
-    "type": "generated-index",
-    "slug": "/development/ask-your-architecture/skills",
-    "description": "Pre-built AI skills for generating EventCatalog documentation"
-  }
-}

package/dist/docs/development/ask-your-architecture/06-slack-integration/01-introduction.md

@@ -1,63 +0,0 @@
----
-sidebar_position: 1
-keywords:
-- Slack Bot
-- Slack Integration
-sidebar_label: Introduction
-title: Slack integration
-description: Query architecture documentation directly from Slack
----
-
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
-The EventCatalog Slack Bot connects to your EventCatalog MCP server, allowing teams to query architecture documentation directly from Slack. Ask questions about events, services, domains, and schemas without leaving your workspace.
-
-The slack bot is self hosted, you own your data and deployment.
-
-<div className="flex justify-center items-center gap-4 flex-col">
-  <img src="/img/slack.png" alt="EventCatalog Slack Bot" className="rounded-lg" style={{ width: '30%', height: 'auto' }} />
-  <span className="text-center text-sm text-gray-500">Example of the EventCatalog Slack Bot in action asking about the OrderCreated event</span>
-</div>
-
-## How it works
-
-1. You configure the bot with your own AI provider and model (e.g. Anthropic, OpenAI, Google)
-1. Users @mention the bot or post in dedicated channels
-2. The bot queries your EventCatalog MCP server
-3. AI-powered responses appear in threads to keep channels organized
-
-## Key features
-
-- **@Mention anywhere** - Add the bot to any channel and ask questions
-- **Dedicated channels** - Create auto-reply channels for architecture questions
-- **Multiple AI providers** - Works with Anthropic, OpenAI, or Google
-- **Self-hosted** - Your data stays private, you control your data and deployment
-- **Socket Mode** - No public URL or webhooks needed
-- **Custom tools support** - Bring your own integrations for real-time data
-
-## Custom tools
-
-The Slack bot supports [custom tools](/docs/development/ask-your-architecture/eventcatalog-assistant/bring-your-own-tools) defined in your `eventcatalog.chat.js` file. This means you can bring real-time data into your Slack conversations:
-
-- Query production metrics from Datadog or Prometheus
-- Check service health and uptime
-- Look up on-call engineers from PagerDuty
-- Fetch queue depths from Kafka
-- Any custom integration your team needs
-
-Custom tools work automatically - the AI decides when to use them based on user questions. Ask "who is on-call for OrderService?" and get live data directly in Slack.
-
-## Prerequisites
-
-- EventCatalog instance (with configured MCP server) running in [SSR mode](/docs/development/deployment/build-ssr-mode)
-- [EventCatalog Scale license](https://eventcatalog.cloud)
-- Slack workspace with app creation permissions
-- API key for your chosen AI provider
-
-## Repository
-
-The EventCatalog Slack Bot is open source:
-
-[github.com/event-catalog/eventcatalog-slack-bot](https://github.com/event-catalog/eventcatalog-slack-bot)

package/dist/docs/development/ask-your-architecture/06-slack-integration/02-slack-app-setup.md

@@ -1,154 +0,0 @@
----
-sidebar_position: 2
-keywords:
-- Slack Bot
-- Slack App
-sidebar_label: Slack app setup
-title: Slack app setup
-description: Create and configure your Slack app
----
-
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
-Create a Slack app to enable the EventCatalog bot in your workspace. You can create the app using a manifest (recommended) or manually configure all settings.
-
-## Create from manifest (recommended)
-
-The fastest way to get started. The manifest automatically configures all required permissions and settings.
-
-### Steps
-
-1. Navigate to [api.slack.com/apps](https://api.slack.com/apps)
-2. Click **Create New App** → **From an app manifest**
-3. Select your workspace and click **Next**
-4. Choose **YAML** and paste this manifest:
-
-```yaml
-display_information:
-  name: EventCatalog Bot
-  description: Query your EventCatalog directly from Slack
-  background_color: "#000000"
-
-features:
-  bot_user:
-    display_name: EventCatalog
-    always_online: true
-
-oauth_config:
-  scopes:
-    bot:
-      - app_mentions:read
-      - chat:write
-      - reactions:read
-      - reactions:write
-      - channels:history
-
-settings:
-  event_subscriptions:
-    bot_events:
-      - app_mention
-      - message.channels
-  interactivity:
-    is_enabled: false
-  org_deploy_enabled: false
-  socket_mode_enabled: true
-  token_rotation_enabled: false
-```
-
-5. Click **Next**, review the summary, and click **Create**
-
-### Get credentials
-
-After creating the app, collect three credentials needed to run the bot.
-
-#### App-Level Token
-
-1. Go to **Basic Information** → **App-Level Tokens**
-2. Click **Generate Token and Scopes**
-3. Name: `socket-mode-token`
-4. Add scope: `connections:write`
-5. Click **Generate** and copy the token (starts with `xapp-`)
-6. Save this as `SLACK_APP_TOKEN`
-
-#### Bot Token
-
-1. Go to **OAuth & Permissions**
-2. Click **Install to Workspace**
-3. Review permissions and click **Allow**
-4. Copy the **Bot User OAuth Token** (starts with `xoxb-`)
-5. Save this as `SLACK_BOT_TOKEN`
-
-#### Signing Secret
-
-1. Go to **Basic Information** → **App Credentials**
-2. Copy the **Signing Secret**
-3. Save this as `SLACK_SIGNING_SECRET`
-
-<details>
-<summary>Setup Slack app manually</summary>
-
-If you prefer to configure settings yourself, follow these steps.
-
-### Create the app
-
-1. Navigate to [api.slack.com/apps](https://api.slack.com/apps)
-2. Click **Create New App** → **From scratch**
-3. Name your app (e.g., "EventCatalog Bot") and select your workspace
-4. Click **Create App**
-
-### Enable Socket Mode
-
-1. Click **Socket Mode** in the left sidebar
-2. Toggle **Enable Socket Mode** to On
-3. Create an App-Level Token when prompted:
-   - Name: `socket-mode-token`
-   - Scope: `connections:write`
-4. Click **Generate**
-5. Copy the token (starts with `xapp-`) - this is `SLACK_APP_TOKEN`
-
-### Configure permissions
-
-1. Click **OAuth & Permissions** in the left sidebar
-2. Scroll to **Scopes** → **Bot Token Scopes**
-3. Add these scopes:
-   - `app_mentions:read` - Receive @mention events
-   - `chat:write` - Send messages
-   - `reactions:read` - Read reactions
-   - `reactions:write` - Add and remove reactions
-   - `channels:history` - Read public channel messages
-
-### Enable events
-
-1. Click **Event Subscriptions** in the left sidebar
-2. Toggle **Enable Events** to On
-3. Expand **Subscribe to bot events**
-4. Add these events:
-   - `app_mention`
-   - `message.channels`
-
-### Install the app
-
-1. Click **OAuth & Permissions** in the left sidebar
-2. Click **Install to Workspace**
-3. Review permissions and click **Allow**
-4. Copy the **Bot User OAuth Token** (starts with `xoxb-`) - this is `SLACK_BOT_TOKEN`
-
-### Get signing secret
-
-1. Click **Basic Information** in the left sidebar
-2. Scroll to **App Credentials**
-3. Copy the **Signing Secret** - this is `SLACK_SIGNING_SECRET`
-
-</details>
-
-## Optional: Private channels and DMs
-
-By default, the bot only reads thread context in public channels. To enable thread context in private channels and DMs, add these additional scopes:
-
-- `groups:history` - Private channels
-- `im:history` - Direct messages
-- `mpim:history` - Group DMs
-
-After adding scopes, reinstall the app to your workspace.