@mermanjs/node 0.8.0-alpha.6 → 0.8.0

package/CHANGELOG.md

@@ -2,9 +2,46 @@
 
 All notable changes to the `@mermanjs/node` package group will be documented in this file.
 
+## [0.8.0] - 2026-10-06
+
+This entry summarizes the candidate package since its introduction during the 0.8 alphas; there was no 0.7.0 Node package. It prepares 0.8.0 and does not announce npm publication. The package group remains experimental and requires Node.js 22 or newer.
+
+### Added
+
+- Choose native `@mermanjs/node` with its exact-version platform package or the explicit `@mermanjs/node-wasm` transport. Both provide deterministic SVG/layout operations; neither silently switches transport or uses browser WASM as a fallback.
+- The current diagram surface includes Agentflow and Usecase. Agentflow follows upstream beta syntax; the package does not add ASCII, analysis, math, binary export, or host text-measurement callbacks.
+
+### Upgrade
+
+- Keep the loader and selected transport artifacts on one package version. Native load failures carry typed ABI/platform diagnostics; resolve these rather than substituting a browser package.
+- Relative to early 0.8 alphas, the candidate selects Mermaid 12.1.0 with Mermaid 12 ELK and Redux/Neo defaults. Review SVG snapshots and explicit top-level layout/theme/look settings. Node rendering is not browser DOM admission.
+
+### Fixed
+
+- Corrected C4 and ELK relationship routing/layering, Packet/XYChart presentation, partial theme overrides, and diagnostic locations; restored Usecase/ER styles and prevented malformed Unicode colors from panicking.
+
+### Further reading
+
+- Use the [package guide](README.md), [stable migration guide](../../docs/release/V070_TO_V080_UPGRADE_GUIDE.md#bindings-and-package-channels), and [root changelog](../../CHANGELOG.md) for the final candidate contract. Native Rust benchmark observations are not Node transport measurements.
+
+## [0.8.0-alpha.7] - 2026-09-30
+
+### Added
+
+- Added Mermaid 12 Agentflow and Usecase parsing and SVG rendering. Agentflow follows upstream beta syntax; neither family supports ASCII output.
+
+### Changed
+
+- Updated the engine from Mermaid 11.17.2 to 12.0.0, including ELK layout defaults and the new theme/look defaults for supported families. Refresh SVG snapshots; use top-level `layout: dagre`, `theme: default`, and `look: classic` when the previous presentation is needed. The bundled artifact already included ELK and retains its EPL-2.0 notices.
+- Safe diagram-local theme variables and fonts are admitted from frontmatter and directives while host security policy remains authoritative.
+
+### Compatibility
+
+- Native and Node-targeted WASM packages remain an experimental Node.js 22+ group. The existing SVG/layout capability recipe does not add ASCII, analysis, math, or raster/PDF export. Update the loader and all selected transport packages together.
+
 ## [0.8.0-alpha.6] - 2026-09-02
 
-This section describes the prepared alpha.6 source candidate. The npm alpha channel remains independently published and may still resolve alpha.5 until the alpha.6 package group is authorized.
+This section describes the published alpha.6 package group. All seven packages, including `@mermanjs/node-wasm`, were manually bootstrapped from the verified package-group artifact. The immutable alpha.6 npm tarballs have no npm provenance; later releases use Trusted Publishing.
 
 ### Added
 

package/README.md

@@ -35,8 +35,7 @@ Create an engine once, reuse it for related work, and dispose it during teardown
 Mermaid-compatible SVG structure for trusted input and parity-sensitive consumers. `parity` is
 not a browser DOM-admission or sanitization check.
 
-For SVG that will be embedded directly into HTML, or when the Mermaid source is not fully trusted,
-select the sealed `resvg-safe` pipeline explicitly:
+For a resvg/usvg consumer that cannot display HTML labels, select `resvg-safe` explicitly:
 
 ```js
 const options = {
@@ -45,8 +44,14 @@ const options = {
 const svg = await engine.renderSvg(source, options);
 ```
 
-The supported pipeline values are `parity`, `readable`, and `resvg-safe`. The safe pipeline can
-remove browser-only SVG features such as active content and `foreignObject` labels. It does not
+The supported pipeline values are `parity`, `readable`, and `resvg-safe`. `readable` is an advanced
+text overlay for consumers that ignore HTML labels; browsers can display both copies and show
+overlapping text. Use `parity` for browser display. `resvg-safe` also removes unsupported styles,
+so it is not a lossless replacement for `readable`. HTML embedding still requires a host-owned
+admission policy; selecting a pipeline alone does not establish browser DOM safety.
+
+The `resvg-safe` pipeline removes browser-only content such as active elements and `foreignObject`
+labels. It does not
 provide browser `Document` or owner-document admission APIs; use `@mermanjs/web*` for browser DOM
 mounting.