etassia 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: be665730fc261fe2a5fd476832ef35e9d408a972e57d8c8fac4e45449865e027
+  data.tar.gz: 9a93797f0daa0959869f5b0341363abf7238a2e039ab018dab823e9e5310169e
+SHA512:
+  metadata.gz: 0fbb0a385089dcabdf9b0a546b5166345d53bf0cee02af4f2681f55c17cda756567eafd7ba1cd8a9b57b5e7d1847e5c6f92fbeb2c7081476f856e5abe160bd4b
+  data.tar.gz: 4a721df6f52a1372cc29de33beca2f0e961b6276dcdbfd4aa3e30d2cb387e8c6ec53e57711f011874eeba8ec036d1a29aba983b5c60a57257777d9583ad0ffab

data/CHANGELOG.md

@@ -0,0 +1,140 @@
+# Changelog
+
+All releasable changes to Etassia are recorded here. The contract each version
+number makes is in [VERSIONING.md](VERSIONING.md).
+
+## Format
+
+- Sections are `## [Unreleased]` first, then `## [X.Y.Z] - YYYY-MM-DD`, newest
+  first.
+- Inside a section, bullets sit under `### Added`, `### Changed`,
+  `### Deprecated`, `### Removed`, `### Fixed` or `### Security`.
+- A change is releasable when it alters what a user of `Etassia.render`,
+  `Engine#render` or the CLI can observe. Refactors, specs and CI are not
+  entries.
+- **Releasable version**: the release preflight
+  (`scripts/check_changelog.rb <next_version>`) passes only when a dated
+  `## [X.Y.Z]` section exists for the version being cut and holds at least one
+  bullet under a category above. Before dispatching a release, a
+  changelog-only PR renames `[Unreleased]` to `[X.Y.Z] - date` and adds a
+  fresh empty `[Unreleased]`. No PR changes `lib/etassia/version.rb`.
+
+## [Unreleased]
+
+### Added
+
+- `Etassia.render` uses the Rust runtime of the optional `etassia-native` gem
+  when it is installed, with the same SVG bytes, and renders in Ruby when it
+  is missing or cannot answer. `ETASSIA_RUNTIME=auto|ruby|rust` selects it.
+- PlantUML `!include FILE[!SELECTOR]`, `!includesub FILE!NAME` and
+  `!startsub`/`!endsub` are expanded. Files are read beside the source's
+  `path:` (or `base_dir:`) and then in `include_path:` or
+  `PLANTUML_INCLUDE_PATH`, never outside those directories. A file that cannot
+  be read raises `Etassia::Notation::PlantUML::Include::Error`.
+
+### Changed
+
+- Etassia now requires Ruby 3.3 or newer and elkrb `~> 2.0`. elkrb 2 itself
+  requires Ruby 3.3.
+
+## [0.2.0] - 2026-10-16
+
+### Added
+
+- Added a notation registry, API notation selection, and CLI `--notation` /
+  repeatable `--require` options for loading notation plugins.
+- Added bundled PlantUML class and sequence rendering, available by loading
+  `etassia/notation/plantuml`.
+- Added `today:` for reproducible date-sensitive rendering and
+  `layout_engine:` for selecting the supported layout placement.
+
+### Changed
+
+- Etassia now requires Ruby 3.2 or newer, elkrb `~> 1.0`, lutaml-model
+  `~> 0.8.0`, kramdown `~> 2.5` and plurimath-parslet `~> 3.0`.
+- `etassia batch` discovers every registered notation's extensions, continues
+  after individual file failures, and exits 1 when any input failed.
+- #62 renamed most of the gem's parser, renderer, layout and diagram-model
+  classes. Every rename below is a plain name change: nothing was removed
+  except where a row says so.
+
+- Diagram model classes (`Etassia::Diagram`):
+
+  | Old name | New name |
+  | --- | --- |
+  | `Diagram::GanttChart` | `Diagram::Gantt` |
+  | `Diagram::QuadrantChart` | `Diagram::Quadrant` |
+  | `Diagram::RadarChart` | `Diagram::Radar` |
+  | `Diagram::ArchitectureDiagram` | `Diagram::Architecture` |
+  | `Diagram::ArchitectureDiagram::Group` | `Diagram::Architecture::Group` |
+  | `Diagram::ArchitectureDiagram::Service` | `Diagram::Architecture::Service` |
+  | `Diagram::ArchitectureDiagram::Edge` | `Diagram::Architecture::Edge` |
+  | `Diagram::SankeyDiagram` | `Diagram::Sankey` |
+  | `Diagram::PacketDiagram` | `Diagram::Packet` |
+  | `Diagram::TreemapDiagram` | `Diagram::Treemap` |
+  | `Diagram::XYChart` | `Diagram::XyChart` |
+  | `Diagram::BlockDiagram` | `Diagram::Block` |
+  | `Diagram::Block` (single block) | `Diagram::BlockNode` |
+  | `Diagram::RequirementDiagram` | `Diagram::Requirement` |
+  | `Diagram::Requirement` (single requirement) | `Diagram::RequirementNode` |
+
+  The last two pairs each reuse a name: the old per-item class moves aside so
+  the whole-diagram class can take its plain name.
+
+- Parser classes (`Etassia::Parser`): every class ending in `Parser` dropped
+  that suffix, e.g. `Parser::FlowchartParser` -> `Parser::Flowchart`. Applies
+  to `Block`, `C4`, `ClassDiagram`, `ErDiagram`, `Error`, `Flowchart`,
+  `Gantt`, `GitGraph`, `Info`, `Kanban`, `Mindmap`, `Packet`, `Pie`,
+  `Quadrant`, `Radar`, `Requirement`, `Sankey`, `Sequence`, `StateDiagram`,
+  `Timeline`, `Treemap`, `UserJourney`. `Parser::XYChartParser` became
+  `Parser::XyChart` (suffix dropped and capitalization changed).
+  `Parser::Architecture` already had a plain name and did not change.
+  `Parser::Grammars::XYChart` became `Parser::Grammars::XyChart`
+  (capitalization only; every other grammar class kept its name).
+
+- Renderer classes (`Etassia::Renderer`): every class ending in `Renderer`
+  dropped that suffix, e.g. `Renderer::FlowchartRenderer` ->
+  `Renderer::Flowchart`. Applies to `Architecture`, `Block`, `C4`,
+  `ClassDiagram`, `ErDiagram`, `Error`, `Flowchart`, `Gantt`, `Info`, `Pie`,
+  `Quadrant`, `Requirement`, `Sankey`, `Sequence`, `StateDiagram`,
+  `Timeline`, `UserJourney`. `Renderer::XYChart` became `Renderer::XyChart`
+  (capitalization only).
+
+- The `Etassia::Transform` module was renamed to `Etassia::Layout`, and every
+  class ending in `Transform` dropped that suffix at the same time, e.g.
+  `Transform::FlowchartTransform` -> `Layout::Flowchart`. Applies to
+  `Architecture`, `Block`, `C4`, `ClassDiagram`, `ErDiagram`, `Error`,
+  `Flowchart`, `Gantt`, `Info`, `Pie`, `Quadrant`, `Requirement`, `Sankey`,
+  `Sequence`, `StateDiagram`, `Timeline`, `UserJourney`. Classes that already
+  had a plain name only moved namespace: `Transform::GitGraph`,
+  `Transform::Kanban`, `Transform::Mindmap`, `Transform::Packet`,
+  `Transform::Radar`, `Transform::Treemap`, `Transform::Base` became
+  `Layout::GitGraph`, `Layout::Kanban`, `Layout::Mindmap`, `Layout::Packet`,
+  `Layout::Radar`, `Layout::Treemap`, `Layout::Base`.
+  `Transform::XYChart` became `Layout::XyChart` (namespace and
+  capitalization). `Transform::TransformError` was removed; its replacement
+  is `Etassia::Layout::LayoutError`.
+
+- The `Etassia::Parser::Transforms` module was renamed to
+  `Etassia::Parser::Builders`; class names inside it did not change, e.g.
+  `Parser::Transforms::Flowchart` -> `Parser::Builders::Flowchart`,
+  `Parser::Transforms::Kanban::BoardBuilder` ->
+  `Parser::Builders::Kanban::BoardBuilder`. `Parser::Transforms::XYChart`
+  became `Parser::Builders::XyChart` (capitalization only, on top of the
+  namespace rename).
+
+### Fixed
+
+- Render every Mermaid case recorded as valid by the pinned oracle in the
+  committed compatibility corpus.
+- Emit well-formed UTF-8 SVG for every committed rendered conformance case,
+  including escaped text and non-UTF-8 process locales.
+- Report invalid input, unknown CLI values, and source-triggered stack or heap
+  exhaustion through Etassia's error and exit-status contracts instead of
+  leaking raw VM failures or failing silently.
+- Honor theme typography, paint and palette roles across the supported
+  Mermaid diagrams, including partial custom themes completed from defaults.
+
+## [0.1.0]
+
+Initial tagged version (`v0.1.0`), released before this changelog existed.

data/LICENSE

@@ -0,0 +1,25 @@
+BSD 2-Clause License
+
+Copyright (c) 2024, Ribose Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.adoc

@@ -0,0 +1,436 @@
+= Etassia
+
+image:https://img.shields.io/gem/v/etassia.svg[RubyGems Version,link=https://rubygems.org/gems/etassia]
+image:https://img.shields.io/github/license/claricle/etassia.svg[License,link=https://github.com/claricle/etassia/blob/main/LICENSE]
+image:https://github.com/claricle/etassia/actions/workflows/rake.yml/badge.svg["Build",link=https://github.com/claricle/etassia/actions/workflows/rake.yml]
+
+== Purpose
+
+Etassia is a pure Ruby interpreter of commonly-used diagram generation languages
+into SVG format.
+
+Etassia currently supports the following diagram definition syntaxes:
+
+// * PlantUML - the text-based UML diagramming language defined by PlantUML
+* Mermaid - the text-based diagramming language defined in mermaid-js
+
+Etassia aims to provide high compatibility with the original tools while offering
+a pure Ruby implementation that can be easily integrated into Ruby-based
+workflows and tools.
+
+NOTE: The name "Etassia" is derived from "Siren", a mythological creature known
+for its enchanting songs that lure sailors, as its usage in multiple languages
+refer to mermaids.
+
+== Implementation notes
+
+The library follows strict object-oriented principles with a model-driven
+architecture. Most diagram models use `Lutaml::Model`, but not all data
+structures do: six diagram classes (`PacketField`, `RadarAxis`, `RadarCurve`,
+`TreemapNode`, `XYAxis`, `XYDataset`) are plain Ruby classes. Six diagram types
+(flowchart, class, state, ER, Sankey, timeline) lay out to a typed
+`Layout::Scene`; the other types still build a graph or legacy layout
+structure. See link:ARCHITECTURE.md[] for the stages.
+
+
+== Features
+
+=== Diagram language support
+
+Mermaid defines a set of diagram type languages for composing different diagram
+types.
+
+Etassia registers 24 diagram types. 23 are Mermaid input languages; the 24th is
+`error`, the fallback Mermaid.js renders when its own parsing fails. Mermaid's
+ZenUML is not registered. Per-type compatibility with real Mermaid.js input
+varies (see below).
+
+// === PlantUML diagram types
+
+=== Mermaid diagram types
+
+Etassia registers 24 Mermaid diagram types end-to-end (parser, transform, and
+renderer). Registration is not the same as full compatibility: the
+per-type pass rates against the mermaid-js corpus are generated from
+`scoreboard/corpus.json` onto the
+https://claricle.github.io/etassia/pages/compatibility/[compatibility page].
+
+* **Flowchart** - Directional graphs with various node shapes and edge types
+* **Sequence diagram** - Message flows between participants over time
+* **Class diagram** - UML class relationships and hierarchies
+* **State diagram** - State machine transitions and hierarchies
+* **Entity-relationship diagram** - Database schema relationships
+* **User journey** - User interaction flows with satisfaction levels
+* **Gantt chart** - Project timelines and task dependencies
+* **Pie chart** - Proportional data visualization
+* **Quadrant chart** - 2D data point categorization
+* **Requirement diagram** - Requirements and their relationships
+* **Git graph** - Git branching and commit history
+* **Mindmap** - Hierarchical mind mapping
+* **Timeline** - Event sequences over time
+* **Sankey diagram** - Flow quantities between nodes
+* **XY chart** - Line and bar charts with axes
+* **Block diagram** - Block-based architecture diagrams
+* **Packet diagram** - Network packet structure
+* **C4 diagram** - Software architecture contexts and containers
+* **Architecture diagram** - Service and component architecture
+* **Kanban board** - Workflow status tracking
+* **Radar chart** - Multi-dimensional data comparison
+* **Treemap** - Hierarchical data as nested rectangles
+* **Error diagram** - Error message display
+* **Info diagram** - Information display
+
+See link:examples/README.adoc[] for working examples of all diagram types.
+
+=== Core capabilities
+
+* **Pure Ruby implementation** - No JavaScript dependencies
+* **Parslet-based parsing** - Declarative grammars with line and column in parse errors
+* **SVG output** - Standards-compliant SVG 1.2
+* **Theme support** - 4 built-in themes, custom theme support
+* **Auto-detection** - Automatic diagram type detection
+* **Batch processing** - Process multiple diagrams at once
+* **CLI tool** - Command-line interface for standalone usage
+* **Programmatic API** - Ruby library for custom workflows
+* **Metanorma-oriented SVG** - Self-contained SVG for embedding in Metanorma
+  documents; flowchart, sequence, class, pie and Gantt renders pass
+  `svg_conform`'s `:metanorma` conformance check with zero errors (checked
+  directly against `SvgConform.validate`; `spec/etassia/svg_conformance_spec.rb`
+  runs this on every suite run against shipped examples, reference
+  fixtures, and the mermaid corpus)
+
+== Installation
+
+=== Via RubyGems
+
+Add Etassia to your Gemfile:
+
+[source,ruby]
+----
+gem 'etassia'
+----
+
+Then execute:
+
+[source,shell]
+----
+bundle install
+----
+
+Or install it directly:
+
+[source,shell]
+----
+gem install etassia
+----
+
+=== Requirements
+
+Ruby 3.3 or higher.
+
+
+== Quick start
+
+=== Command-line usage
+
+Render a single Mermaid diagram to SVG:
+
+[source,shell]
+----
+etassia render diagram.mmd -o output.svg
+----
+
+Create a PlantUML class diagram in `diagram.puml`:
+
+----
+@startuml
+class User
+class Account
+User --> Account : owns
+@enduml
+----
+
+Then render it by loading the bundled notation:
+
+----
+etassia render --require etassia/notation/plantuml diagram.puml -o output.svg
+----
+
+The same notation renders PlantUML sequence diagrams. Create
+`sequence.puml`:
+
+----
+@startuml
+Alice -> Bob : hello
+Bob --> Alice : hi
+@enduml
+----
+
+Then render it the same way:
+
+----
+etassia render --require etassia/notation/plantuml sequence.puml -o sequence.svg
+----
+
+Render all Mermaid files in a directory:
+
+[source,shell]
+----
+etassia batch -i input_dir/ -o output_dir/
+----
+
+List all supported diagram types:
+
+[source,shell]
+----
+etassia types
+----
+
+=== Programmatic usage
+
+Use Etassia in your Ruby code:
+
+[source,ruby]
+----
+require 'etassia'
+
+# Render from a string
+mermaid_code = <<~MERMAID
+  graph TD
+    A[Start] --> B[Process]
+    B --> C[End]
+MERMAID
+
+svg = Etassia.render(mermaid_code)
+File.write('output.svg', svg)
+
+# Render from a file
+svg = Etassia.render(File.read('diagram.mmd'))
+File.write('output.svg', svg)
+
+# Pick a built-in theme
+svg = Etassia.render(mermaid_code, theme: 'dark')
+----
+
+==== Optional Rust runtime
+
+When the optional `etassia-native` gem (the Rust runtime from
+https://github.com/claricle/etassia-rs[claricle/etassia-rs]) is installed,
+`Etassia.render` with no options renders Mermaid sources through it. The SVG
+bytes are the same as the Ruby pipeline's. Without the gem, for an
+option-bearing render, for a diagram type the Rust runtime has not ported, or
+when it reports an error, Etassia renders in Ruby, so errors are always the
+Ruby exceptions. `etassia-native` is not a dependency of this gem.
+
+`ETASSIA_RUNTIME` selects the runtime: `auto` (default), `ruby` (never use
+Rust) or `rust` (raise `Etassia::Engine::PipelineError` instead of falling back).
+
+=== Examples
+
+Browse link:examples/README.adoc[] for 53 example sources across all 24
+diagram types; 52 have a tracked SVG (one `.beta.mmd` source does not render yet).
+
+== Documentation
+
+Documentation is available at the
+https://claricle.github.io/etassia[Etassia Documentation Site].
+
+=== Quick links
+
+* https://claricle.github.io/etassia/pages/comparison/[Tool Comparison] - Compare Etassia with Mermaid.js, PlantUML, and Graphviz
+* https://claricle.github.io/etassia/pages/compatibility/[Mermaid.js Compatibility] - Detailed syntax compatibility matrix
+* https://claricle.github.io/etassia/diagram_types/[Diagram Types Reference] - Complete syntax reference for all 24 diagram types
+
+=== Documentation Structure
+
+The documentation uses a 6-collection architecture:
+
+. **Core Topics** - Compatibility and comparison
+. **Tutorials** - Step-by-step learning paths
+. **Guides** - Task-oriented how-to documentation
+. **Diagram Types** - Complete reference for all 24 diagram types with examples
+. **Features** - Detailed capability documentation
+. **References** - Reference index
+
+See the https://claricle.github.io/etassia[documentation site] for the complete guide.
+
+
+== Architecture
+
+=== General
+
+Etassia implements a pipeline architecture that transforms Mermaid source
+code through distinct processing stages, each with clear responsibilities and
+well-defined interfaces.
+
+**All parsers use Parslet**, a powerful PEG (Parsing Expression Grammar) library
+that provides composability and declarative grammars. The 3-layer Parslet
+architecture (Grammar → Builder → Parser) is not universal: 10 of the 26 files
+under `lib/etassia/parser/builders/` subclass `Parslet::Transform`, the rest are
+plain classes or helpers, and User Journey builds its
+model directly in the parser.
+
+Layout uses a built-in fallback grid (`Layout::Grid`) by default. Flowcharts
+can be placed by the elkrb gem instead with `layout_engine: :elk`. Etassia is a pure Ruby
+implementation with no JavaScript dependencies, generating standards-compliant
+SVG 1.2 output suitable for direct integration with Metanorma documentation
+frameworks.
+
+.Etassia processing pipeline
+[source]
+----
+Mermaid Syntax Input (String)
+         │
+         ▼
+    ┌─────────┐
+    │ Parser  │  Parslet Grammar → Transform → Parser
+    └────┬────┘  (3-layer architecture)
+         │
+         ▼
+   ┌───────────┐
+   │ Diagram   │  Lutaml::Model AST
+   │   Model   │  (Flowchart, Sequence, etc.)
+   └─────┬─────┘
+         │
+         ▼
+   ┌───────────┐
+   │Transform  │  Diagram → Graph Conversion
+   │  Layer    │
+   └─────┬─────┘
+         │
+         ▼
+   ┌───────────┐
+   │  Layout   │  Position Computation
+   │  Engine   │  (Node positions, edge routes)
+   └─────┬─────┘
+         │
+         ▼
+   ┌───────────┐
+   │    SVG    │  Graph → SVG Conversion
+   │ Renderer  │
+   └─────┬─────┘
+         │
+         ▼
+   ┌───────────┐
+   │    SVG    │  Lutaml::Model Structure
+   │  Builder  │
+   └─────┬─────┘
+         │
+         ▼
+  SVG XML Output (String)
+----
+
+.Component relationships
+[source]
+----
+Etassia (Root Module)
+    │
+    ├── Engine (Orchestrator)
+    │     ├── coordinates overall flow
+    │     ├── delegates to Parser
+    │     ├── delegates to Transform
+    │     └── delegates to Renderer
+    │
+    ├── Parser (Parslet-based Syntax Analysis)
+    │     ├── Grammars (Parslet rules)
+    │     ├── Transforms (tree conversion)
+    │     └── produces Diagram Models
+    │
+    ├── Diagram (Domain Models)
+    │     ├── Architecture
+    │     ├── Block
+    │     ├── C4
+    │     ├── ClassDiagram
+    │     ├── ErDiagram
+    │     ├── Error
+    │     ├── Flowchart
+    │     ├── Gantt
+    │     ├── GitGraph
+    │     ├── Info
+    │     ├── Kanban
+    │     ├── Mindmap
+    │     ├── Packet
+    │     ├── Pie
+    │     ├── Quadrant
+    │     ├── Radar
+    │     ├── Requirement
+    │     ├── Sankey
+    │     ├── Sequence
+    │     ├── StateDiagram
+    │     ├── Timeline
+    │     ├── Treemap
+    │     ├── UserJourney
+    │     └── XyChart
+    │
+    ├── Transform (Model Conversion)
+    │     └── diagram-specific converters
+    │
+    ├── Renderer (SVG Generation)
+    │     └── diagram-specific renderers
+    │
+    ├── Svg (SVG Models)
+    │     ├── Document, Element, Group
+    │     ├── Path, Text, Rect
+    │     └── Circle, Line, Polygon
+    │
+    └── DiagramRegistry (Type Registration)
+          └── maps types to handlers
+----
+
+=== Parslet-based parser architecture
+
+All 24 implemented diagram types use Parslet for grammar parsing, but only 10 of
+the 26 files under `lib/etassia/parser/builders/` subclass `Parslet::Transform`. Where the 3-layer pattern is
+followed it looks like this:
+
+. **Layer 1: Grammar** (Parslet::Parser) - Defines syntax rules using Parslet
+  DSL, parses text into intermediate tree structures
+. **Layer 2: Builder** (Parslet::Transform) - Converts intermediate trees to
+  typed Diagram models using pattern matching
+. **Layer 3: Parser** - Orchestrates Grammar and Transform, provides public API
+
+Several types deviate: `lib/etassia/parser/builders/architecture.rb` and
+`lib/etassia/parser/builders/class_diagram.rb` (among other builders under
+`lib/etassia/parser/builders/`) are plain Ruby classes rather than
+`Parslet::Transform` subclasses, and `Etassia::Parser::UserJourney#parse`
+builds its diagram model directly from the parse tree without a separate
+Transform layer.
+
+This architecture provides:
+
+* **Line and column in parse errors** (for example `Parse error at line 9, column 8`)
+* **Composability** through shared grammar rules across diagram types
+* **Maintainability** via declarative, self-documenting syntax rules
+* **Typed models** (Lutaml::Model) for most diagram types
+
+See link:ARCHITECTURE.md[] for detailed architecture documentation.
+
+== Test coverage
+
+=== General
+
+Etassia's test suite exercises the extracted mermaid-js corpus (`spec/mermaid/`)
+across all registered diagram types. The `mermaid:validate` rake task
+(`tasks/generate_mermaid_fixtures.rake`) checks only that
+`Etassia.render` runs without raising on each corpus source; it does not
+compare output against mermaid-cli reference SVGs. Comparison against
+mermaid-cli-generated reference output is a separate, optional task
+(`rake mermaid:compare`, not run in CI or the default suite) — see
+"Mermaid-js compatibility validation" below.
+
+=== Mermaid-js compatibility validation
+
+`spec/fixtures_mermaid/` contains 847 unique mmdc-generated reference SVGs
+(each duplicated into a `correct/` subdirectory, so a naive file count reads
+~1,694); no automated spec currently compares rendered output against them.
+
+// === PlantUML compatibility validation
+
+// Etassia includes a large number of PlantUML compatibility test cases to ensure
+// seamless integration with PlantUML syntax for supported diagram types.
+
+== Copyright and license
+
+Copyright Ribose.
+
+This software is licensed under the BSD-2-Clause license.

data/exe/etassia

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require_relative "../lib/etassia"
+require_relative "../lib/etassia/cli"
+
+Etassia::Cli.start(ARGV)