@eventcatalog/core 5.0.0-beta.9 → 5.0.1

package/dist/docs/development/bring-your-own-documentation/custom-pages/03-components.md

@@ -8,10 +8,6 @@ title: Components
 description: Component list for custom pages 
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 You can add custom EventCatalog components to your custom pages.
 
 [See the list of components and how to use them](/docs/development/components/using-components).

package/dist/docs/development/bring-your-own-documentation/custom-pages/04-owners.md

@@ -10,10 +10,8 @@ description: Adding owners to custom pages with EventCatalog.
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.33.0" />
-<PlanBanner plan="Scale" />
 
 Owners in EventCatalog are either **users** or **teams** and are **optional**.
 

package/dist/docs/development/bring-your-own-documentation/resource-docs/01-introduction.md

@@ -11,10 +11,8 @@ keywords:
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
-<AddedIn version="3.15.0" />
-<PlanBanner plan="Scale" />
+<AddedIn version="3.15.1" />
 
 Resource-level documentation lets you attach documentation pages directly to any resource in your catalog. Instead of keeping ADRs, runbooks, contracts, and guides in a separate tool, you can place them alongside the resource they describe.
 

package/dist/docs/development/bring-your-own-documentation/resource-docs/02-adding-resource-docs.md

@@ -11,11 +11,9 @@ keywords:
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import ProjectTree from '@site/src/components/MDX/ProjectTree';
 
-<AddedIn version="3.15.0" />
-<PlanBanner plan="Scale" />
+<AddedIn version="3.15.1" />
 
 ## Adding resource-level documentation
 
@@ -63,7 +61,6 @@ Each doc file supports the following frontmatter.
 | `order`   | No       | Explicit sort position within the group.        |
 | `badges`  | No       | Badges shown on the doc page.                   |
 
-
 #### Example of resource-level documentation
 
 ```mdx title="services/OrdersService/docs/01-deployment.mdx"

package/dist/docs/development/bring-your-own-documentation/resource-docs/03-categories.md

@@ -10,11 +10,9 @@ keywords:
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import ProjectTree from '@site/src/components/MDX/ProjectTree';
 
 <AddedIn version="2.x.0" />
-<PlanBanner plan="Scale" />
 
 When you group resource docs into subdirectories, each subdirectory becomes a section in the resource sidebar. By default, the section label is the folder name and sections are sorted alphabetically.
 

package/dist/docs/development/bring-your-own-documentation/resource-docs/04-versioning.md

@@ -9,11 +9,9 @@ keywords:
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import ProjectTree from '@site/src/components/MDX/ProjectTree';
 
-<AddedIn version="3.15.0" />
-<PlanBanner plan="Scale" />
+<AddedIn version="3.15.1" />
 
 ## How versioning works
 

package/dist/docs/development/components/components/11-flow.md

@@ -32,6 +32,21 @@ Embed flows into your pages.
 | `search` (optional)             | `boolean`  | `false`           | Show or hide the search bar in the flow. Accepts `true`/`false` or `"true"`/`"false"`. |
 | `walkthrough` (optional)             | `boolean`  | `false`           | Show or hide the step walkthrough controls. Accepts `true`/`false` or `"true"`/`"false"`. |
 | `mode` (optional)             | `string` ("simple" or "full")  | `"simple"`           | `simple` renders the flow in a simplified view without descriptions. `full` renders descriptions and other information.|
+| `lanes` (optional)             | `string` (`"domain"`, `"system"`, `"team"` or `"domain-system"`)  | (empty)           | Start the flow with its steps grouped by domain, system, team, or domains with their systems nested inside. Groups are drawn as boxes. Added in 5.0.0. |
+
+### Start a flow grouped
+
+<AddedIn version="5.0.0" />
+
+Use `lanes` to embed a flow with its steps already grouped. Groups come from your catalog: each step's domain, system and owning team.
+
+```jsx /domains/Orders/index.mdx
+<Flow id="place-an-order" lanes="team" />
+```
+
+The groups are drawn as boxes around their steps. Readers can switch to lanes, or group the flow another way, from the **Group by** menu. If the flow has no groups of that kind (for example no step belongs to a team), or the value isn't one of the four above, the flow renders ungrouped. A `group` parameter in the page URL takes priority over `lanes`.
+
+Read more about [grouping flows](/docs/development/guides/resources/flows/explore-flows#group-steps-by-domain-system-or-team).
 
 :::tip Multiple embeds per page
 You can embed multiple `<Flow />` components on the same page and each one renders independently.
@@ -46,6 +61,8 @@ Flow visualizations include the same interactive controls as NodeGraph component
 
 Switch between React Flow and Mermaid view modes, export as Mermaid diagram code, or share URLs with your team.
 
+Flows also have a **Group by** menu in the top right (or press <kbd>G</kbd>) to group the steps by domain, system, team, or domain then system, drawn as boxes or lanes. The Mermaid view and export leave the groups out. See [Explore flows](/docs/development/guides/resources/flows/explore-flows).
+
 [Read more about interactive controls](/docs/development/components/components/nodegraph#interactive-controls)
 
 Flow visualizations also support [layout persistence](/docs/development/components/components/nodegraph#layout-persistence) in dev mode, allowing you to save custom node positions.

package/dist/docs/development/components/components/15-nodegraph.md

@@ -11,7 +11,9 @@ import AddedIn from '@site/src/components/MDX/AddedIn';
 
 A component to visually render your information.
 
-The `<NodeGraph/>` component is supported in domains, services, and all messages, changelogs, and custom documentation pages.
+The `<NodeGraph/>` component is supported in domains, systems, services, and all messages, changelogs, and custom documentation pages.
+
+On a domain page, `<NodeGraph/>` renders the domain's [Diagram](/docs/development/guides/domains/visualize-domains/domain-diagram), opening at level 1 (the domain, its systems, and the domains it talks to).
 
 ### Single NodeGraph
 
@@ -44,17 +46,44 @@ All NodeGraph visualizations include interactive controls for better viewing, ex
 
 ![NodeGraph interactive controls](./img/interactive-controls.png)
 
-### View modes
+### Canvas toolbar
+
+<AddedIn version="5.0.0" />
+
+A floating toolbar sits at the bottom of the canvas. It has:
+
+- **L1**, **L2** and **L3**: the levels of detail. They are the same on every diagram:
+  - **L1**: domains, systems and their relationships.
+  - **L2**: services and data stores.
+  - **L3**: adds messages and channels.
+- Tools for the resource shown. For example, a domain's Diagram page has **Highlight cross-domain communication**, which picks out the edges to and from other domains.
+- **Simulate messages**: animates messages moving along the edges.
+- **Show minimap** / **Hide minimap**.
+- **Fit to view**: zooms to fit the whole diagram.
+
+Levels a diagram doesn't have are greyed out. For example, L1 is greyed out on a service's diagram, which has no domains or systems to show. Hover a greyed out level to see why.
+
+The level is kept in the URL (`?level=1`, `?level=2` or `?level=3`), so a shared link opens at the same level. The level you pick is remembered for each kind of diagram. Flows and entity diagrams don't show levels.
 
-Switch between two visualization modes using the view switcher dropdown.
+### Legend
 
-**React Flow** - Interactive node-based visualization with drag and pan controls.
+Click an entry in the legend to hide those nodes from the diagram, and click it again to show them. The diagram lays itself out again without them, and the entry fades while hidden. When you hide messages or channels, the nodes on either side stay connected.
 
-**Mermaid** - Standard Mermaid diagram view with automatic layout and pan/zoom controls.
+Hidden entries stay hidden when you switch levels.
 
-### Export as Mermaid
+### Canvas menu
 
-Copy the NodeGraph as Mermaid diagram code to your clipboard. The diagram preserves all nodes, edges, and styling information.
+Open the menu (three dots next to the diagram title) and select **Canvas** for these options:
+
+- **Render as mermaid**: switch between the interactive diagram and a Mermaid diagram with automatic layout and pan/zoom controls.
+- **Simulate Messages**: animate messages moving along the edges.
+- **Hide channels**: hide channel nodes.
+- **Hide messages**: hide messages and channels. This is the same view as level 2.
+- **Show minimap**, **Fit to view** and **Find on canvas**.
+
+### Copy as Mermaid {#export-as-mermaid}
+
+Select **Copy as mermaid** in the menu to copy the NodeGraph as Mermaid diagram code to your clipboard. The diagram preserves all nodes, edges, and styling information.
 
 Useful for sharing architectures with LLMs, documentation tools, or pasting into Mermaid-compatible renderers like [mermaid.live](https://mermaid.live).
 
@@ -62,9 +91,9 @@ Useful for sharing architectures with LLMs, documentation tools, or pasting into
 If you export large NodeGraphs and they fail to render as Mermaid diagrams, increase the `maxTextSize` configuration. [Learn more about maxTextSize](/docs/api/config#mermaid).
 :::
 
-### Share URL
+### Share Link
 
-Copy the current page URL to share the visualization with your team.
+Select **Share Link** in the menu to copy a link to the visualization and share it with your team.
 
 ## Layout persistence
 
@@ -103,7 +132,11 @@ This deletes the saved layout file and reloads the page with auto-calculated pos
 
 Layout files are keyed by resource (collection/id/version), so the same layout is used whether viewing in the visualizer or embedded in documentation.
 
-Works across all visualizers including services, events, flows, domains, entity maps, and designs.
+Works across all visualizers including services, events, flows, domains, systems, entity diagrams, and designs.
+
+:::note Layouts from before v5
+Domain and system diagrams are laid out differently in EventCatalog v5. Layouts saved for the old domain and system Resource Diagram pages don't carry over to the new Diagram pages. Layouts saved for a system's context diagram carry over to level 1 of its Diagram.
+:::
 
 **Example layout file structure:**
 

package/dist/docs/development/components/components/18-remote-schema.md

@@ -10,7 +10,6 @@ title: RemoteSchema
 description: Component for fetching and rendering remote schemas in EventCatalog
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
 <AddedIn version="2.52.0" />
@@ -49,8 +48,6 @@ The `<RemoteSchema/>` component only works in Server-Side Rendering (SSR) mode.
 
 ### Fetching from Private APIs
 
-<PlanBanner plan="Scale" />
-
 For private APIs requiring authentication, you can provide headers:
 
 ```jsx /events/MyEvent/index.mdx
@@ -105,7 +102,7 @@ The component automatically detects JSON Schema format and renders an interactiv
 | `url` (required)        | `string`  | (empty)           | The URL to fetch the schema from. Supports environment variable templating with `${VAR_NAME}` syntax. |
 | `title` (optional)      | `string`  | "Remote Schema"   | Title to display above the schema                                 |
 | `maxHeight` (optional)  | `string`  | "400"             | Maximum height of the schema viewer in pixels                    |
-| `headers` (optional)    | `object`  | `{}`              | HTTP headers for authentication (requires EventCatalog Scale plan) |
+| `headers` (optional)    | `object`  | `{}`              | HTTP headers for authentication                                   |
 | `jsonPath` (optional)   | `string`  | (empty)           | [JSONPath expression](https://github.com/dchester/jsonpath) to extract specific parts of the response    |
 | `renderAs` (optional)   | `string`  | "auto"            | Rendering mode: "auto", "schema", or "raw"                      |
 

package/dist/docs/development/components/custom-components/07-reference.md

@@ -31,6 +31,20 @@ import ServiceCard from '@catalog/components/service-card.astro';
 | `.astro` | Reusable UI, props, data fetching, browser scripts, and styling |
 | `.mdx` | Reusable Markdown content |
 
+### React components
+
+React components in your catalog's `components` directory run on React 19 from EventCatalog v5.
+
+If a component uses an API that React 19 removed, update it before you upgrade:
+
+- `defaultProps` on function components: use default values in the props instead.
+- `propTypes`: remove them, or use TypeScript for prop types.
+- String refs: use `useRef` or callback refs.
+- `ReactDOM.render`: use `createRoot` from `react-dom/client`.
+- `findDOMNode`: use a ref to the DOM element.
+
+Read the [React 19 upgrade guide](https://react.dev/blog/2024/04/25/react-19-upgrade-guide) for the full list of changes.
+
 ## Astro component structure
 
 Astro components have a component script and a component template.

package/dist/docs/development/customization/02-themes.md

@@ -11,8 +11,6 @@ title: Themes
 description: Customize the look and feel of your catalog with built-in themes, dark/light mode, and custom themes
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
 EventCatalog comes with a selection of built-in themes and supports both light and dark modes out of the box.
 
 ## Choosing a theme
@@ -38,7 +36,6 @@ EventCatalog includes the following built-in themes:
 | `sunset` | Orange accent - warm and energetic |
 | `forest` | Dark green accent - natural and grounded |
 
-
 ## Light and dark mode
 
 EventCatalog supports both light and dark modes. Users can toggle between modes using the theme switcher in the header.
@@ -61,8 +58,6 @@ If no preference is stored, EventCatalog automatically follows the user's system
 
 ## Creating custom themes
 
-<PlanBanner plan="Scale" />
-
 Custom themes allow you to fully brand EventCatalog with your organization's colors. You define your theme in `eventcatalog.styles.css` using CSS variables.
 
 ### Step 1: Create your theme CSS

package/dist/docs/development/customization/03-search.md

@@ -13,7 +13,7 @@ description: Configure resource metadata search or opt-in to full-content indexe
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-<AddedIn version="3.36.0" />
+<AddedIn version="3.36.1" />
 
 EventCatalog ships with two search modes. The default is a fast metadata search that works with no extra configuration. An opt-in indexed mode adds full-content search powered by [Pagefind](https://pagefind.app/).
 

package/dist/docs/development/customization/05-custom-pages-and-api-routes/01-introduction.md

@@ -11,10 +11,8 @@ description: Understand custom pages and API routes in EventCatalog.
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="4.1.1" />
-<PlanBanner plan="Scale" />
 
 EventCatalog gives you a structured catalog out of the box, but every organization eventually needs pages that are specific to how they work.
 

package/dist/docs/development/customization/05-custom-pages-and-api-routes/04-reference.md

@@ -91,7 +91,13 @@ export default {
 };
 ```
 
-If EventCatalog finds API routes in `pages/api` during a static build, the build fails and asks you to enable server mode or remove the `pages/api` directory.
+If EventCatalog finds API routes in `pages/api` during a static build, the build fails and asks you to enable server mode or remove the `pages/api` directory. `eventcatalog dev` still serves the routes, and logs the same message as a warning.
+
+:::info Upgrading from v4
+
+In v4, catalogs without a Scale license skipped custom pages, so a static build with a `pages/api` directory still passed. From v5, custom pages are served for every catalog, and a static build with `pages/api` fails until you set `output: 'server'` or remove the directory.
+
+:::
 
 ## Import aliases
 

package/dist/docs/development/customization/05-resource-sidebar.md

@@ -124,7 +124,7 @@ Because a `$token` inside `pages` splices in that section's items, extending a g
   "title": "Quick Reference",
   "icon": "BookOpen",
   "pages": [
-    // Splices in the generated Quick Reference items (Overview, Changelog, ...)
+    // Splices in the generated Quick Reference items (Overview, Resources, Changelog, ...)
     "$quick-reference",
     // ...followed by your own pages
     "[[doc|guides/onboarding]]",

package/dist/docs/development/customization/09-embed-eventcatalog.md

@@ -8,26 +8,19 @@ keywords:
   - iframe
   - developer portal
   - internal application
-  - Scale
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 You can embed EventCatalog pages in developer portals, internal tools, intranets, and other web applications. Your teams can explore architecture information in the application where they already work while EventCatalog remains the source of the documentation.
 
-Embedding EventCatalog requires an EventCatalog Scale license. See [Getting a license key for EventCatalog Scale](/docs/development/license-keys/plans).
-
 ## What you can embed
 
 | Feature | What users can do in the embedded view |
 | --- | --- |
 | Resource documentation | Read the documentation for a domain, system, service, message, flow, team, or another catalog resource. |
-| Resource visualizer | Explore the selected resource and its relationships. |
+| Resource visualizer | Explore the selected resource and its relationships, at the levels its diagram supports. |
 | Architecture Graph | Explore the catalog-wide graph or focus it on a resource with a relationship depth of 1, 2, or 3. |
-| System Context Maps | View the catalog-wide system overview or the context surrounding one system. |
-| Entity maps | Explore the entities and relationships associated with a resource. |
+| System Context Diagram | View the catalog-wide system overview or the context surrounding one system. |
+| Entity Diagram | Explore the entities and relationships associated with a resource. |
 | Flows | Follow the steps, services, and messages in a business or technical flow. |
 | Discovery tables | Browse and filter catalog resources such as services, events, commands, and queries. |
 | Schema explorer | Search schemas, inspect their contents, and see the resources that use them. |
@@ -52,7 +45,6 @@ The requested theme only affects that embedded page. It does not replace the vis
 
 ## Before you embed
 
-- Build and deploy EventCatalog with a valid Scale license.
 - Use an EventCatalog URL that users of the host application can reach from their browsers.
 - If EventCatalog is authenticated, verify that users can authenticate from the embedded context.
 - Give the iframe's parent a defined height. EventCatalog fills the space the host application provides.
@@ -119,17 +111,30 @@ Replace `https://catalog.example.com` with the URL of your deployed catalog.
 | Resource documentation | `/docs/{collection}/{id}/{version}?embed=true` |
 | Resource visualizer | `/visualiser/{collection}/{id}/{version}?embed=true` |
 | Discovery table | `/discover/{collection}?embed=true` |
-| Entity map | `/visualiser/{collection}/{id}/{version}/entity-map?embed=true` |
-| Data dependency view | `/visualiser/{collection}/{id}/{version}/data?embed=true` |
+| Entity Diagram | `/visualiser/{collection}/{id}/{version}/entity-map?embed=true` |
 | Schema explorer | `/schemas/explorer?embed=true` |
 | Schema details | `/schemas/{type}/{id}/{version}?embed=true` |
 | Architecture Graph | `/visualiser/graph?embed=true` |
-| System Context Map overview | `/visualiser/system-context-map?embed=true` |
-| System-specific context map | `/visualiser/systems/{id}/{version}/context?embed=true` |
+| System Context Diagram overview | `/visualiser/system-context-map?embed=true` |
+| System diagram | `/visualiser/systems/{id}/{version}?embed=true` |
 | Flow visualizer | `/visualiser/flows/{id}/{version}?embed=true` |
 
 Collections use their plural route names, such as `domains`, `systems`, `services`, `events`, `commands`, `queries`, `flows`, and `entities`. Schema detail pages support message types such as `events`, `commands`, and `queries`, as well as data product contracts.
 
+### Open a diagram at a level
+
+Visualizer diagrams have three levels: `1` for domains, systems and their relationships, `2` for services and data stores, and `3` adding messages and channels. Add `level` to open the embedded diagram at a level:
+
+```text
+https://catalog.example.com/visualiser/domains/Payments/1.0.0?embed=true&level=2
+```
+
+:::info Upgrading from v4
+
+The service data dependency view (`/data`), the system context view (`/context`) and the domain systems view (`/systems-context`) now redirect to a level of the resource's diagram. The redirect drops the query string, including `embed=true`, so update embedded URLs to the diagram URL with a `level` instead.
+
+:::
+
 ### Focus the Architecture Graph
 
 Use `focus={collection}/{id}` to select the initial resource and `depth` to choose how many relationship hops are visible. `depth` accepts `1`, `2`, or `3`.
@@ -152,16 +157,6 @@ module.exports = {
 
 ## Troubleshooting
 
-### EventCatalog shows a license overlay
-
-Confirm that the deployed catalog was built or started with a valid Scale license. Add the key to the EventCatalog project's environment:
-
-```bash title=".env"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-Then rebuild and redeploy the catalog. See [Getting a license key for EventCatalog Scale](/docs/development/license-keys/plans).
-
 ### Navigation is still visible
 
 Confirm that the URL contains `embed=true`, including the exact lowercase value `true`.

package/dist/docs/development/deployment/hosting-options.md

@@ -86,10 +86,15 @@ ENV HOST=0.0.0.0
 ENV PORT=3000
 EXPOSE 3000
 
-# Start the server
-CMD npm run start
+# Start the server. The exec form (a JSON array) passes `docker stop` (SIGTERM) on to the server,
+# so it stops straight away rather than being killed after Docker's timeout.
+CMD ["npm", "run", "start"]
 ```
 
+:::tip
+Use the exec form of `CMD` (`CMD ["npm", "run", "start"]`) rather than the shell form (`CMD npm run start`). With the shell form, a shell runs as the container's first process and doesn't pass signals on, so `docker stop` and Kubernetes pod shutdowns wait for their timeout and then kill the server.
+:::
+
 Then you can build the docker image with:
 
 ```bash

package/dist/docs/development/developer-tools/eventcatalog-linter/how-to/05-fix-common-problems.md

@@ -68,6 +68,22 @@ The path in `schemaPath`, `schemas[]`, `specifications` or a data product contra
 
 For `styles.icon`, paths starting with `/` are checked against the catalog's `public/` folder. If your static assets live elsewhere, set `['error', { publicDir: 'static' }]` or disable icon checks with `{ icons: false }`.
 
+## "… leads to step …, but the flow has no step with that id"
+
+```
+13:16 ✖ error Step "start" leads to step "paymnet", but the flow has no step with that id. [steps[0].next_step] (refs/flow-step-exists)
+```
+
+A flow step's `next_step` or `next_steps` points at a step that isn't in the flow, usually a typo. Correct the id so it matches another step's `id` in the same flow.
+
+## "Step … points at … A step can only be one thing"
+
+```
+9:5 ✖ error steps.0.service: Step "checkout" points at message and service. A step can only be one thing, so split it into two steps. [steps.0.service] (schema/required-fields)
+```
+
+A flow step uses more than one node type. EventCatalog fails the build on this. Split it into one step per node type and connect them with `next_step`. The same applies to a step that has both `next_step` and `next_steps`: keep one.
+
 ## "version: Expected string, but received undefined"
 
 ```

package/dist/docs/development/developer-tools/eventcatalog-linter/reference/03-rules.md

@@ -23,6 +23,7 @@ Rules are grouped into five categories. Each rule can be set to `'error'`, `'war
 | [`refs/valid-version-range`](#refsvalid-version-range) | error | |
 | [`refs/channel-exists`](#refschannel-exists) | error | |
 | [`refs/container-exists`](#refscontainer-exists) | error | |
+| [`refs/flow-step-exists`](#refsflow-step-exists) | error | |
 | [`refs/file-exists`](#refsfile-exists) | error | `icons`, `publicDir` |
 | [`refs/orphan-messages`](#refsorphan-messages) | warn | |
 | [`best-practices/summary-required`](#best-practicessummary-required) | error | |
@@ -49,6 +50,15 @@ A required field is missing from the frontmatter. Which fields are required depe
 
 **Fix:** add the field.
 
+This rule also reports flow steps that use more than one node type (for example `message` and `service`), or both `next_step` and `next_steps`. EventCatalog 5 fails the build on both.
+
+```
+9:5 ✖ error steps.0.service: Step "checkout" points at message and service. A step can only be one thing, so split it into two steps. [steps.0.service] (schema/required-fields)
+19:5 ✖ error steps.1.next_steps: Step "pay" has both next_step and next_steps. Use next_step for one next step, or next_steps for several. [steps.1.next_steps] (schema/required-fields)
+```
+
+**Fix:** split the step into one step per node type, and use `next_step` for one next step or `next_steps` for several. See [Model flow steps](/docs/development/guides/resources/flows/model-flow-steps#mistakes-in-flow-steps).
+
 ### `schema/valid-type`
 
 A field has the wrong type — a string where a list is expected, a missing required field reported as `undefined`, and so on.
@@ -119,6 +129,14 @@ The same check for keys inside nested objects and arrays (`sends[0].too`, `detai
 
 Arbitrary keys are permitted where the schema allows them — flow step `custom.properties`, channel `parameters`, and any `producers`/`consumers` object.
 
+:::warning Unknown flow step properties fail the build
+From EventCatalog 5.0.0, unknown properties on a flow step (such as `steps[1].servce`) fail the build unless they start with `x-`. The linter still reports them under this rule, as a warning by default. To catch them as errors, promote the rule for your flows with an [override](../how-to/configure-rules#apply-different-rules-to-different-folders), for example `overrides: [{ files: ['**/flows/**'], rules: { 'schema/unknown-nested-field': 'error' } }]`.
+
+```
+15:5 ⚠ warning Unknown property "steps[1].servce". Did you mean "service"? [steps[1].servce] (schema/unknown-nested-field)
+```
+:::
+
 ## Reference validation
 
 These rules check that everything your frontmatter points at actually exists. References can be plain ids (`- order-service`) or objects (`- id: order-service`, optionally with `version`). Version matching follows the [versions reference](./versions).
@@ -159,7 +177,7 @@ The referenced resource exists, but no version of it satisfies the reference. Th
 
 ### `refs/channel-exists`
 
-A channel referenced from `sends[].to`, `receives[].from`, a message's `channels`, or a channel's `routes`/`channels` doesn't exist (or doesn't exist at that version).
+A channel referenced from `sends[].to`, `receives[].from`, a message's `channels`, a channel's `routes`/`channels`, or a flow step's `channel` doesn't exist (or doesn't exist at that version).
 
 ```
 11:9 ✖ error Referenced channel "orders-topic" does not exist. Did you mean "orders"? [sends[0].to[0]] (refs/channel-exists)
@@ -173,6 +191,18 @@ A container referenced from `writesTo`, `readsFrom`, a system's `containers`, or
 13:5 ✖ error Referenced container "orders-db" does not have a version matching "9.0.0". Available versions: 1.0.0 [writesTo[0]] (refs/container-exists)
 ```
 
+### `refs/flow-step-exists`
+
+<AddedIn version="1.2.0" pkg="@eventcatalog/linter" url="https://github.com/event-catalog/eventcatalog" />
+
+A flow step's `next_step` or `next_steps` points at a step id that isn't in the flow. EventCatalog leaves the arrow out of the diagram and logs a warning, so a typo here quietly breaks the flow.
+
+```
+13:16 ✖ error Step "start" leads to step "paymnet", but the flow has no step with that id. [steps[0].next_step] (refs/flow-step-exists)
+```
+
+**Fix:** correct the id so it matches the `id` of another step in the same flow, or add the missing step.
+
 ### `refs/file-exists`
 
 <AddedIn version="1.1.17" pkg="@eventcatalog/linter" url="https://github.com/event-catalog/eventcatalog" />

package/dist/docs/development/developer-tools/eventcatalog-linter/reference/05-supported-resources.md

@@ -65,7 +65,7 @@ All resources are checked for frontmatter schema conformance, unknown keys, owne
 | Service, Agent | `sends`, `receives` (incl. channels), `writesTo`, `readsFrom`, `flows`, `entities` (services only) |
 | Event, Command, Query | `producers`, `consumers`, `channels`, `messageChannels`; orphan detection; `schemaPath` / `schemas[]` files |
 | Channel | `channels`, `routes`, `messages` |
-| Flow | each step's `message`, `service`, `agent`, `flow`, `container`, `dataProduct` |
+| Flow | each step's `message`, `service`, `agent`, `system`/`systems`, `channel`, `flow`, `container`, `dataProduct`; each step's `next_step`/`next_steps` points at a step in the flow |
 | Entity | `properties[].references`, `services`, `domains` |
 | Container | `services`, `servicesThatWriteToContainer`, `servicesThatReadFromContainer`, `dataProductsThatWriteToContainer`, `dataProductsThatReadFromContainer` |
 | Data product | `inputs`, `outputs` (any linkable type), `outputs[].contract.path` file |

package/dist/docs/development/governance/architecture-change-detection/01-introduction.md

@@ -5,20 +5,12 @@ title: Architecture Change Detection
 description: Know when your event-driven architecture changes. Get notified when services start or stop producing and consuming messages.
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 Services get added. Consumers change. Producers disappear. In event-driven systems, these relationship changes often go unnoticed until something breaks downstream.
 
 **Architecture Change Detection** compares your catalog across branches and tells you exactly what changed: which services started consuming a message, which stopped producing one, and who is affected.
 
 You can configure webhooks to send notifications to tools like Slack or PagerDuty when changes are detected, including relationship changes, deprecations, and schema updates. Rules can also be configured to block CI/CD pipelines entirely using the `fail` action.
 
-:::info Scale plan required
-Architecture Change Detection requires an [EventCatalog Scale plan](https://eventcatalog.dev/pricing).
-:::
-
 ## How it works
 
 1. Define rules in `governance.yaml` at the root of your catalog
@@ -58,5 +50,3 @@ This rule detects whenever any service starts or stops consuming any message, an
 
 Using the [`status` field](/docs/development/governance/architecture-change-detection/ci-cd#include-a-status-label) you can choose to detect changes that are proposed vs approved. This can be useful when you want to detect changes that are proposed vs approved in your architecture.
 
-
-

package/dist/docs/development/governance/architecture-change-detection/06-pipeline-gates.md

@@ -7,10 +7,6 @@ description: Block merges automatically when governance rules trigger
 
 Use the `fail` action to exit the CLI with code `1`, turning governance checks into hard gates that prevent merges when architectural rules are violated. Without `fail`, triggered rules only notify -- the CLI always exits `0`.
 
-:::info Scale plan required
-Architecture Change Detection requires an [EventCatalog Scale plan](https://eventcatalog.dev/pricing).
-:::
-
 ## Add the fail action
 
 Add `type: fail` to any rule that should block the pipeline. The `message` field is optional but recommended -- it explains to the developer exactly what needs to happen before the PR can merge.

package/dist/docs/development/guides/97-architecture-graph.md

@@ -13,7 +13,7 @@ import AddedIn from '@site/src/components/MDX/AddedIn';
 
 <AddedIn version="4.5.0" />
 
-The architecture graph is a force-directed view of every resource in your catalog and the relationships between them. Unlike the [system context map](/docs/development/guides/systems/system-context-maps), which needs systems to exist, the architecture graph works for any catalog.
+The architecture graph is a force-directed view of every resource in your catalog and the relationships between them. Unlike the [System Context Diagram](/docs/development/guides/systems/system-context-maps), which needs systems to exist, the architecture graph works for any catalog.
 
 Use this view when you want to answer questions like:
 

package/dist/docs/development/guides/99-adding-analytics.md

@@ -5,11 +5,8 @@ title: Adding Analytics
 description: Track page views and user behavior across your catalog
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-<PlanBanner plan="Scale" />
-
 EventCatalog supports analytics integrations that let you track how your team navigates and uses your catalog. Connect your existing analytics tools to understand which services, events, and flows your team visits most.
 
 Three providers are supported: **Google Analytics 4**, **Google Tag Manager**, and **PostHog**. Multiple providers can be enabled at the same time.
@@ -131,7 +128,3 @@ Custom events are forwarded to all configured providers simultaneously.
 ## Missing an integration?
 
 If you need support for an analytics provider not listed here, [open a GitHub issue](https://github.com/boyney123/eventcatalog/issues) or [join the Discord community](https://discord.gg/3rjaZMmrAm) and let us know. We are always looking to expand our integrations based on what teams are using.
-
-:::info Scale plan required
-Analytics integrations require an [EventCatalog Scale plan](https://eventcatalog.dev/pricing). If you configure integrations without a valid license, a warning is shown during build.
-:::

package/dist/docs/development/guides/domains/03-model-subdomains.md

@@ -24,8 +24,8 @@ _See [subdomain example](https://demo.eventcatalog.dev/docs/domains/E-Commerce/1
 
 #### Domains Visualizer (with subdomains)
 
-When you reference a subdomain from a domain, it will appear in the domains visualizer.
-You can use the legend to highlight resources that are part of a subdomain.
+When you reference a subdomain from a domain, it will appear in the domain's [Diagram](/docs/development/guides/domains/visualize-domains/domain-diagram).
+Subdomains are shown as domains inside the parent domain, with their own systems and services. At level 1, a subdomain without systems is shown as a single card.
 
 ![Domains Visualizer (with subdomains)](../img/domains/subdomain-visualizer.png)