@r0kshan/cairn 1.0.0-RC11 → 1.0.0-RC12

package/README.md

@@ -31,7 +31,7 @@ Furthermore, complexe software architecture with many flows and component genera
 | **Configurable dispositions** | `slide` and `page` dispositions available to suit different presentation requirements |
 | **Spacial optimization** | Cairn aims to optimize space as much as possible (Still working on improving this functionnality) |
 | **Typed diagrams with validation.** | Each view defines its element kinds and rules; `cairn validate` reports syntax, schema, and completeness issues as source-located, coded diagnostics, with a JSON mode for CI. |
-| **Infrastructure flow matrix.** | `cairn matrix` exports the flow matrix as CSV, Markdown, or SVG. Columns split protocol from port, annotate each endpoint with its network zone, and localise via `style { lang: fr }`. |
+| **Flow matrix.** | `cairn matrix` exports the flow matrix as CSV, Markdown, or SVG — from any view, with the columns that view can fill. In infrastructure it splits protocol from port and annotates endpoints that sit in a network zone; headers localise via `style { lang: fr }`. The same table is available to embedders through `compile(source, { matrix: true })`. |
 | **Enterprise-view extras.** | Business objects on flows, an auto-generated legend, and a numbered-flow table via `flow-text: numbered`. |
 | **French or English output.** | `style { lang: fr }` localizes band titles, legend, and matrix headers while keeping keywords English for portable sources (open to adding other languages if you find this usefull) |
 | **In-built themes and customizable colours** | Whether using the default or a chosen in-built theme, element colours can be overriden  for all elements of a given kind in the `style` block |
@@ -174,15 +174,8 @@ brew install R0kshan/tap/cairn
 # Windows — Scoop
 scoop bucket add cairn https://github.com/R0kshan/scoop-bucket
 scoop install cairn
-
-# npm (requires Node ≥ 22.6)
-npm i -g @r0kshan/cairn@unstable
 ```
 
-> `@unstable` is not optional: cairn is pre-stable, so tagged versions publish to
-> that dist-tag and there is no `latest` yet — a bare `npm i -g @r0kshan/cairn`
-> fails with `No matching version found` until the first stable release.
-
 From source (no release needed — requires Node ≥ 22.6):
 
 ```sh
@@ -234,6 +227,8 @@ On validation errors nothing is written and the exit code is 1; warnings are pri
 cairn matrix my-infra.cairn --format csv    # csv (default) | md | svg · -o to set the path
 ```
 
+Every view exports one; the columns follow the view (infrastructure keeps protocol and port, application keeps the protocol alone, logical keeps just the exchange).
+
 ### Rebuild on every save
 
 ```sh

package/THIRD-PARTY-NOTICES.md

@@ -12,8 +12,13 @@ theirs is distributed.
 Version 0.12.0, inlined unmodified. Upstream: https://github.com/kieler/elkjs
 
 Declared license: `EPL-2.0 OR GPL-3.0-or-later`. cairn elects **EPL-2.0** — full
-text at https://www.eclipse.org/legal/epl-2.0/ and in `LICENSE.md` inside the
-elkjs package.
+text in [`licenses/elkjs-EPL-2.0.md`](./licenses/elkjs-EPL-2.0.md), a verbatim
+copy of elkjs' own `LICENSE.md`, upstream at https://www.eclipse.org/legal/epl-2.0/.
+
+That copy is vendored rather than referenced because elkjs is a *devDependency*:
+the published package installs zero dependencies, so `node_modules/elkjs/` never
+reaches a consumer while the inlined code does. EPL-2.0 §3.1(b) requires the
+license to travel with the distributed form, so `files` ships it in the tarball.
 
 Per EPL-2.0 §3.1(a): the source code for elkjs is available under the EPL-2.0,
 and can be obtained from https://github.com/kieler/elkjs or from the published
@@ -26,6 +31,7 @@ covers cairn's own code only.
 
 ---
 
-If the set of inlined dependencies changes, update this file in the same commit.
-`files` in `package.json` ships it with the npm package; it lives in the repo for
-every other channel.
+If the set of inlined dependencies changes, update this file **and** `licenses/`
+in the same commit — a notice that names a license text the tarball doesn't carry
+is the failure mode this section exists to prevent. `files` in `package.json`
+ships both with the npm package.