Diagram export

Use bluep generate diagram <dir> [--area <name>] --format svg|pdf --out <file> to write a deterministic vector diagram. Both --format and --out are required. The command prints the written path on success.

SVG exports one complete diagram. It uses the same renderer as generated documentation, so an area SVG has identical entity, relationship, notation, stereotype, review, and classification markup.

PDF exports the selected area. Without --area, it writes one page per subject area in name order. A model with no subject areas produces one page named All. Pages use A3 landscape dimensions and standard vector fonts; they contain no raster image.

For example:

bluep generate diagram devdata/models/commerce --area Sales --format svg --out Sales.svg
bluep generate diagram devdata/models/commerce --format pdf --out commerce.pdf

The browser editor requests compact diagram metadata before it asks for a viewport. Metadata contains only entity rectangles, allowing the minimap and search index to work without creating a DOM node for every entity.

The interactive stage requests a bounded rectangle with a rendering margin. The server caches the deterministic layout per subject area and model generation, then returns only visible entities and qualifying relationships. Edits and reloads invalidate that cache.

Use the search field to find entity names case-insensitively. Prefix matches appear before other substring matches. Selecting a result centres it in the current viewport, while the minimap can recenter the diagram directly.

Zoom is constrained to keep navigation practical on both sparse and dense models. The stage always replaces its single SVG rather than accumulating prior viewport content.

This keeps browser interaction responsive even when the model contains thousands of entities.