feat(spa): vendor Vue frontend + emit bundle in both output modes

.github/workflows/frontend.yml

@@ -0,0 +1,47 @@
+name: Frontend build check
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'frontend/**'
+      - '.github/workflows/frontend.yml'
+  pull_request:
+    paths:
+      - 'frontend/**'
+      - '.github/workflows/frontend.yml'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build-check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: frontend/package-lock.json
+
+      - name: Install
+        working-directory: frontend
+        run: npm ci
+
+      - name: Build
+        working-directory: frontend
+        run: npm run build
+
+      - name: Dist matches committed
+        run: |
+          # `npm run build` rewrites dist/. If anything differs from
+          # what's committed, ask the contributor to rebuild and
+          # commit dist/ as part of the same PR.
+          if ! git diff --exit-code --stat frontend/dist; then
+            echo "::error::frontend/dist/ is out of date. Run 'cd frontend && npm install && npm run build' and commit the result."
+            git diff --stat frontend/dist
+            exit 1
+          fi

.gitignore

@@ -15,3 +15,7 @@
 
 # Test artifacts from CLI invocations without --output
 *.svg
+
+# Frontend (Vue) — node_modules is local only; dist/ is committed so
+# the gem ships with a pre-built bundle and never needs npm at install.
+/frontend/node_modules/

TODO.diagrams/01-svg-measurement-harness.md

@@ -0,0 +1,31 @@
+# TODO-D 01 - SVG measurement harness
+
+## Status: COMPLETE (2026-07-26)
+
+## What was built
+
+`spec/support/parity/checker.rb` — `Parity::Checker` compares two
+SVG strings and reports per-metric deltas (rect, path, polygon,
+text, group counts, font family match, view box match, text overlap
+ratio).
+
+`spec/support/parity/suite.rb` — `Parity::Suite` runs the checker
+across every diagram in a Document that has a matching reference
+SVG, aggregating per-diagram results into a SuiteReport with
+shape-count totals, text-overlap average, and outlier detection.
+
+## Why spec/support/ not lib/
+
+These are test-only utilities — they exist to verify our emitter
+against reference SVGs and have no production purpose. Keeping them
+out of lib/ preserves the production/test boundary.
+
+## Usage
+
+```ruby
+require "parity/suite"
+suite = Parity::Suite.new(document, ref_dir).measure
+suite.aggregate_shape_counts  # => { ours: {...}, reference: {...} }
+suite.text_overlap_avg        # => 0.62
+suite.outliers                # => [DiagramReport, ...]
+```

TODO.diagrams/02-polygon-over-rendering.md

@@ -0,0 +1,29 @@
+# TODO-D 02 - Polygon over-rendering
+
+## Status: COMPLETE (2026-07-26)
+
+## Root cause
+
+Two bugs caused polygon over-rendering:
+
+1. **Markers emitted one polygon per connector, even when multiple
+   connectors ended at the same anchor** (e.g., 9 inheritance arrows
+   converging on a single base class produced 9 identical triangle
+   polygons).
+
+2. **Floating-point waypoint precision caused "identical" markers
+   to differ in their point strings** (e.g., `683.37 2041.37` vs
+   `683.39 2043.35`), defeating naive `body.uniq` deduplication.
+
+## Fix
+
+`Markers#layers` now deduplicates by **rounded anchor point** —
+the first coordinate pair of each polygon/path, rounded to integer.
+Two markers anchored at the same integer pixel are treated as
+duplicates regardless of their other point values.
+
+## Impact (full plateau measurement)
+
+| Metric | Before | After |
+|---|---|---|
+| Polygon delta vs ref | +442 (46% over) | -10 (parity) |

TODO.diagrams/03-text-over-rendering.md

@@ -0,0 +1,30 @@
+# TODO-D 03 - Text over-rendering
+
+## Status: COMPLETE (2026-07-26)
+
+## Root cause
+
+The tagged values compartment was rendered unconditionally for
+every classifier that had tagged values, regardless of the
+diagram's actual display configuration. The reference SVGs only
+show tagged values when the per-element style has `Tag=1`.
+
+The previous fix (TODO 70) added the TaggedValueRenderer but did
+not gate it on the element-level Tag flag.
+
+## Fix
+
+`Elements#groups_for` now reads `element.show_tagged_values`
+(parsed from the per-element style `Tag=0/1` field) and only
+renders the tagged value compartment when the flag is set.
+
+The `DiagramElement` model gained `show_tagged_values` boolean.
+`ExtensionStyleParser` populates it from the `Tag=` style key.
+`DiagramBuilder` passes it through to the model.
+
+## Impact (full plateau measurement)
+
+| Metric | Before | After |
+|---|---|---|
+| Text delta vs ref | +5134 (29% over) | -252 (parity) |
+| Text overlap avg | 57% | 62% |

TODO.diagrams/04-rect-under-rendering.md

@@ -0,0 +1,33 @@
+# TODO-D 04 - Rect under-rendering
+
+## Status: WONTFIX (data drift) (2026-07-26)
+
+## Investigation
+
+Across 185 plateau diagrams, we under-render 221 rects (11%). The
+worst case (bldg_1) shows 18 rects in reference vs 11 in ours —
+7 missing rects.
+
+Examining bldg_1's reference SVG reveals classifiers placed on the
+diagram (e.g., `uro::ReservoirFloodingRiskAttribute`) that are NOT
+in the XMI's `<diagram>/<elements>` block. The classifier exists
+in the uml:Model hierarchy, but no `<element subject="..."/>` ref
+places it on this diagram.
+
+## Conclusion
+
+The reference SVGs were generated from a MORE COMPLETE XMI than
+the one we have. The XMI/SVG pair has drift — the SVG has
+placements the XMI doesn't carry.
+
+This is a fixture data issue, not an emitter bug. We cannot render
+elements the XMI doesn't place. Closing this gap requires either:
+
+1. Regenerating the plateau XMI from the same QEA source that
+   produced the reference SVGs.
+2. Implementing a "implicit placement" mode that auto-places
+   classifiers referenced by connectors but not in `<elements>`.
+   This would be guesswork — we don't know where EA placed them.
+
+Option 1 is the right path. Marking this wontfix pending fixture
+regeneration.

TODO.diagrams/05-canvas-dimension-parity.md

@@ -0,0 +1,51 @@
+# TODO-D 05 - Canvas dimension parity
+
+## Status: PARTIAL (2026-07-26)
+
+## Current state
+
+| | Avg delta | Range |
+|---|---|---|
+| Width | +87px | -403 to +1482 |
+| Height | +576px | -109 to +4833 |
+
+For diagrams where XMI matches reference content (small delta),
+the canvas is consistently ~20-25 px wider and ~7-15 px taller
+than reference. That delta is the frame margin.
+
+## Frame margin rule
+
+Reference SVGs use non-uniform frame margins around element
+bounds:
+
+- Left:   35 px (body left to canvas left)
+- Right:  50 px (body right to canvas right)
+- Top:    60 px (body top to canvas top)
+- Bottom: 36 px (body bottom to canvas bottom)
+
+These come from EA's frame outer border (6 px from canvas edge)
+plus an additional 29/44/54/30 px inset for the body. The asymmetry
+exists because:
+
+- Top: extra space for the frame tab label (extends from y=6 to
+  y=26 plus padding to body_top=60).
+- Right/bottom: extra space for shadow / image padding.
+
+## Fix attempted
+
+`BoundsCalculator#compute` already reserves 20 px above each
+Package element for the tab polygon. Adding frame-aware padding
+to all four sides would close the per-diagram gap on small
+diagrams.
+
+## Why deferred
+
+The 576 px average height delta dwarfs the frame margin issue.
+Most of the height over-rendering is from XMI/SVG drift (we render
+elements the reference SVG doesn't show). Until that's resolved
+(fixture regeneration — see TODO-D 04), fixing the frame margin
+won't move the aggregate metric meaningfully.
+
+The small-diagram match (those closest to reference) shows the
+frame margin fix would close ~5-10 px of the remaining 20-25 px
+delta. Not enough to justify the added complexity right now.

TODO.diagrams/06-group-layering-parity.md

@@ -0,0 +1,39 @@
+# TODO-D 06 - Group layering parity
+
+## Status: PARTIAL (2026-07-26)
+
+## Current state
+
+EA emits each `<rect>`, `<polygon>`, `<path>`, `<text>` inside its
+own `<g>` block with a specific `style` attribute. Style strings
+differ by:
+
+- stroke_width (1 vs 2)
+- stroke_linecap (round vs square)
+- stroke_linejoin (bevel vs miter)
+- fill color
+- stroke color
+- opacity
+
+Our emitter groups output by `style_key` (a Symbol like
+`:diamond_filled` or `:triangle_open`), with the style string
+looked up from a small dispatch table. This matches EA's grouping
+semantics for most cases.
+
+## Note element body
+
+The Note element body was previously emitted as a `<polygon>`. EA
+emits it as a closed `<path d="M...L...Z"/>` with
+`stroke-linejoin=bevel` and `stroke-linecap=square`. Fixed in
+commit f4fa55f.
+
+## Remaining gap
+
+EA sometimes uses different `stroke-linecap` for the same shape
+type depending on whether it's a "decorative" element (square cap)
+or a "connector" element (round cap). Our style dispatch table
+doesn't distinguish these. Visible in:
+
+- Note bodies (square) vs classifier rects (round) — fixed
+- Connector lines (round) vs divider lines (round) — both round
+- Visibility icon rects inside attribute compartments — TBD

TODO.diagrams/07-text-content-fidelity.md

@@ -0,0 +1,65 @@
+# TODO-D 07 - Full text content fidelity
+
+## Status: PARTIAL (62% overlap) (2026-07-26)
+
+## Current state
+
+Text overlap (Jaccard index of text content sets between our SVG
+and reference SVG):
+
+- Average across 185 plateau diagrams: **62%**
+- Best diagrams: ~95%
+- Worst diagrams: ~20%
+
+## What's working
+
+- Classifier names and stereotypes render correctly when the
+  element is placed on the diagram.
+- Attribute text matches when the element has Tag=0 (no tagged
+  values compartment).
+- Visibility prefixes ("+ ", "- ") match.
+- Multiplicity brackets match.
+
+## What's still off
+
+### 1. Tagged value visibility (mostly fixed, edge cases remain)
+Reference SVGs don't render the "tags" header compartment except
+on 2 diagrams. Our Tag-flag gating brought text overlap from 41%
+to 62%. Remaining misses are likely from elements where the
+`Tag=1` flag is set but the reference still doesn't render tags
+— possibly tied to stereotype source (profile-applied vs
+user-defined tagged values).
+
+### 2. Qualified name vs simple name
+Reference uses qualified names like
+`uro::TrafficVolumeAttribute`. Our output sometimes uses the
+short name only. The qualified_name attribute is set on the
+Classifier model, but the renderer doesn't always pick it up
+correctly when the element is placed on a sub-package diagram.
+
+### 3. Attribute ordering
+Within a classifier's attribute compartment, EA sorts attributes
+by some criteria (possibly visibility then alphabetical). Our
+ordering follows the XMI's `ownedAttribute` order, which may
+differ.
+
+### 4. Attribute visibility color
+Reference uses different fill colors for public/protected/private
+attributes (`#66413F` for some, `#595959` for others). Our
+renderer uses a single text color from the theme.
+
+## Path to 100% text overlap
+
+1. Characterize the tagged value visibility rule by examining
+   which elements with `Tag=1` still don't render tags in
+   reference (estimated 5-10 diagrams).
+
+2. Always use `classifier.qualified_name` for the header label
+   (currently mixed).
+
+3. Sort attributes by visibility prefix, then alphabetical.
+
+4. Apply theme.color_for_attribute_visibility for attribute text.
+
+Each of these is a separate fix. None require architectural
+changes.

TODO.diagrams/08-qea-direct-pipeline.md

@@ -0,0 +1,46 @@
+# TODO-D 08-11 - QEA-direct pipeline
+
+## Status: COMPLETE (2026-07-27)
+
+## What was wired
+
+1. **TODO-D 08**: QEA DiagramBuilder propagates StyleEx to
+   Diagram.style_ex. Theme=:119 is now correctly detected from QEA.
+
+2. **TODO-D 09**: IdNormalizer.to_eaid converts `{GUID}` to
+   `EAID_<guid-with-underscores>` for matching reference SVG
+   filenames. The QEA stores diagram GUIDs in braces-dashes form;
+   the reference SVGs use the EAID_ underscore form.
+
+3. **TODO-D 10**: New QEA NoteBuilder parses t_object rows with
+   object_type="Note" or "Text". These render as Package-shaped
+   diagram boxes (not dog-eared Notes — QEA's "Note" type is a
+   diagrammatic Package-shape box for free text, distinct from
+   XMI's uml:Note).
+
+   Also: connector_type from t_connector.Type is now propagated
+   to DiagramConnector so Marker::Diamond matches Aggregation
+   and Composition (was being dropped, all connectors fell back
+   to Association).
+
+4. **TODO-D 11**: spec/ea/svg/qea_regression_spec.rb renders all
+   188 diagrams directly from the QEA against reference SVGs.
+   Passes at the 60 percent within-tolerance threshold.
+
+## Parity delta from QEA-direct fixes
+
+| Metric | Before | After |
+|---|---|---|
+| Polygon delta | n/a (was reading XMI) | -166 (was -842 at start) |
+| Path delta | n/a | -181 |
+| Text overlap avg | 10% (initial QEA-direct) | 56% |
+| Within tolerance | 60.6% | 65.4% |
+
+## Bonus fixes shipped alongside
+
+- ClassifierBuilder no longer prepends package name to
+  qualified_name (QEA t_object.Name already includes the prefix).
+- HeaderLines no longer renders fallback stereotype labels.
+- AttributeRenderer no longer double-colons type names.
+- bounds_from_rect uses min/max of rect values (QEA stores rect
+  with recttop > rectbottom).