ea 0.3.1 → 0.5.0

data/TODO.fixup/51-promote-theme-to-ea-namespace.md

@@ -0,0 +1,28 @@
+# 51 - Promote Theme to Ea::Theme Top-Level Namespace
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Theme is currently `Ea::Svg::EaEmitter::Theme` — buried inside the
+SVG emitter. But Theme is a DOMAIN concept (visual style), not
+rendering-specific. Other consumers (HTML docs, image rendering,
+documentation generation) will also need themes.
+
+The current placement violates MECE: Theme logic is mixed with
+SVG rendering concerns.
+
+## What needs to change
+
+1. New `Ea::Theme` module at top level (in `lib/ea/theme.rb`)
+2. Move `Ea::Svg::EaEmitter::Theme` → `Ea::Theme::Definition`
+3. Move `Ea::Svg::EaEmitter::ThemeRegistry` → `Ea::Theme::Registry`
+4. Move `Ea::Svg::EaEmitter::ThemeColors` → merge into Definition
+5. Backward-compat aliases in EaEmitter (temporary)
+
+## Acceptance
+
+- Ea::Theme module exists with autoloads for Definition, Registry
+- Ea::Svg::EaEmitter::Theme aliases to Ea::Theme::Definition
+- All existing specs pass
+- New spec verifies the namespace move

data/TODO.fixup/52-theme-definition-integrated-fills.md

@@ -0,0 +1,26 @@
+# 52 - Theme::Definition with Integrated Fills
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+`ThemeColors` is a separate module mapping classifier types to
+fill colors. This is a Theme concern — the colors ARE part of the
+theme definition. Currently they're scattered across two modules.
+
+## What needs to change
+
+1. `Ea::Theme::Definition` gains a `fills` attribute (Hash:
+   classifier class name → hex color)
+2. `#fill_for(classifier)` method on Definition returns the
+   per-type fill or nil
+3. `#with(**overrides)` method returns a new Definition with the
+   specified fields overridden (immutable editing pattern)
+4. Built-in :default and :119 themes include their fills inline
+
+## Acceptance
+
+- Definition has `fills` Hash attribute
+- Definition#fill_for(classifier) returns correct color per type
+- Definition#with(**overrides) returns new Definition
+- All existing specs pass

data/TODO.fixup/53-theme-registry-yaml-loading.md

@@ -0,0 +1,50 @@
+# 53 - Theme::Registry with YAML Loading
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Current `ThemeRegistry` has built-in themes hard-coded as Ruby
+constants. Like `stereotype_colors.yml`, themes should be
+externalized to YAML files for easy editing.
+
+## What needs to change
+
+1. `Ea::Theme::Loader` loads a YAML file into a Definition
+2. `Ea::Theme::Registry.load_dir(path)` loads all themes from
+   a directory (one YAML file per theme)
+3. `config/themes/` directory holds theme definition files:
+   - `default.yml` — no theme (uses element-stored values)
+   - `119.yml` — Carlito 7pt, gray text, purple-gray borders
+4. Registry auto-loads from `config/themes/` on first access
+
+## YAML format
+
+```yaml
+id: "119"
+name: EA White Theme
+font:
+  family: Carlito
+  size: 7
+  unit: pt
+text:
+  color: "#595959"
+  weight_normal: 0
+  weight_bold: 700
+border:
+  color: "#9A8484"
+  stroke_width: 1
+fills:
+  Klass: "#FDFAF7"
+  Interface: "#F1ECFA"
+  DataType: "#FAF9E6"
+  Enumeration: "#E8FDE3"
+  PrimitiveType: "#FAF9E6"
+```
+
+## Acceptance
+
+- config/themes/default.yml and 119.yml exist
+- Registry.load_dir loads them
+- YAML format matches Definition fields
+- New spec covers YAML loading

data/TODO.fixup/54-diagram-theme-api.md

@@ -0,0 +1,50 @@
+# 54 - Diagram#theme and #theme= API
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Currently `Diagram` has `theme_id` (string from style_ex) but
+no way to get or set the resolved Theme Definition object. Users
+cannot:
+- Get the active theme: `diagram.theme`
+- Set a theme: `diagram.theme = :119`
+- Override theme on a specific diagram: `diagram.theme = custom_def`
+
+## What needs to change
+
+1. `Diagram#theme` — returns resolved Definition:
+   - theme_override if set
+   - Registry.lookup(theme_id) otherwise
+   - Registry::DEFAULT if neither
+2. `Diagram#theme=(value)` — accepts:
+   - `Ea::Theme::Definition` instance → sets theme_override
+   - String ID (":119") → sets theme_id, clears override
+   - Symbol ID (:119) → sets theme_id, clears override
+3. `Diagram#theme_override` — stores explicit Definition
+4. JSON mapping for theme_id and theme_override
+
+## Usage
+
+```ruby
+# Read theme
+diagram.theme  # → Ea::Theme::Definition
+
+# Set by ID
+diagram.theme = :119
+diagram.theme = ":119"
+
+# Set custom definition
+diagram.theme = Ea::Theme::Definition.new(id: "custom", ...)
+
+# Edit existing theme (immutable → new instance)
+diagram.theme = diagram.theme.with(text_color: "#FF0000")
+```
+
+## Acceptance
+
+- Diagram#theme returns Definition
+- Diagram#theme= accepts Definition, String, Symbol
+- Diagram#theme_override stores explicit Definition
+- JSON round-trip preserves theme_id and theme_override
+- New specs cover all access patterns

data/TODO.fixup/55-update-eaemitter-to-ea-theme.md

@@ -0,0 +1,23 @@
+# 55 - Update EaEmitter to Use Ea::Theme Namespace
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+After promoting Theme to Ea::Theme (TODO 51), the EaEmitter must
+reference the new paths. ColorResolver, FontResolver, Elements,
+and LayerSequencer all reference `ThemeRegistry.lookup(diagram.theme_id)`.
+
+## What needs to change
+
+1. All `Ea::Svg::EaEmitter::ThemeRegistry` → `Ea::Theme::Registry`
+2. All `Ea::Svg::EaEmitter::Theme` → `Ea::Theme::Definition`
+3. `Diagram#theme` (from TODO 54) replaces `ThemeRegistry.lookup(diagram.theme_id)`
+4. ColorResolver and FontResolver accept `Definition` directly
+5. Keep backward-compat aliases in EaEmitter (deprecated)
+
+## Acceptance
+
+- EaEmitter references Ea::Theme::*
+- diagram.theme used everywhere (replacing manual Registry lookup)
+- All existing specs pass

data/TODO.fixup/56-theme-yaml-files.md

@@ -0,0 +1,65 @@
+# 56 - Theme Definition YAML Files
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Theme definitions should be in human-editable YAML files (like
+`stereotype_colors.yml`), not hard-coded Ruby constants.
+
+## What needs to change
+
+1. `config/themes/default.yml` — no theme override
+2. `config/themes/119.yml` — EA White Theme (Carlito 7pt)
+3. Both follow the YAML format defined in TODO 53
+4. Ea::Theme::Loader auto-loads from config/themes/ on first
+   Registry access
+
+## default.yml
+
+```yaml
+id: default
+name: Default (element-stored values)
+font:
+  family: null
+  size: null
+  unit: px
+text:
+  color: "#000000"
+  weight_normal: 400
+  weight_bold: 700
+border:
+  color: "#000000"
+  stroke_width: 2
+fills: {}
+```
+
+## 119.yml
+
+```yaml
+id: "119"
+name: EA White Theme
+font:
+  family: Carlito
+  size: 7
+  unit: pt
+text:
+  color: "#595959"
+  weight_normal: 0
+  weight_bold: 700
+border:
+  color: "#9A8484"
+  stroke_width: 1
+fills:
+  Ea::Model::Klass: "#FDFAF7"
+  Ea::Model::Interface: "#F1ECFA"
+  Ea::Model::DataType: "#FAF9E6"
+  Ea::Model::Enumeration: "#E8FDE3"
+  Ea::Model::PrimitiveType: "#FAF9E6"
+```
+
+## Acceptance
+
+- Both YAML files exist and parse correctly
+- Loader loads them into Registry
+- Registry.lookup("119") returns Definition with all fields

data/TODO.fixup/57-theme-specs-and-integration.md

@@ -0,0 +1,27 @@
+# 57 - Theme Specs and Integration Test
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+The Theme refactor (TODO 51-56) is a major architectural change.
+Comprehensive specs are needed to verify:
+1. YAML loading
+2. Definition immutability + #with
+3. Registry OCP (register new themes)
+4. Diagram#theme API (get/set/override)
+5. Integration: render with custom theme
+
+## What needs to change
+
+1. `spec/ea/theme/definition_spec.rb` — value object behavior
+2. `spec/ea/theme/registry_spec.rb` — registry + YAML loading
+3. `spec/ea/theme/loader_spec.rb` — YAML parsing
+4. `spec/ea/model/diagram_theme_spec.rb` — Diagram#theme API
+5. Integration spec: render with custom theme, verify output
+
+## Acceptance
+
+- All spec files created with comprehensive coverage
+- >90% line coverage on Ea::Theme::*
+- All existing specs pass

data/TODO.fixup/58-ea-entry-point-theme-autoload.md

@@ -0,0 +1,20 @@
+# 58 - EA::Ea.rb Entry Point Autoload for Theme
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+`Ea::Theme` is a new top-level namespace. It needs proper autoload
+registration in `lib/ea.rb` (the gem entry point).
+
+## What needs to change
+
+1. `lib/ea/theme.rb` — module entry file with autoloads
+2. `lib/ea.rb` adds `autoload :Theme, "ea/theme"`
+3. All Theme sub-files follow autoload pattern
+
+## Acceptance
+
+- `require "ea"` makes `Ea::Theme::*` available
+- No require_relative in any Theme file
+- All autoloads defined in `lib/ea/theme.rb`

data/TODO.fixup/59-thread-theme-through-all-renderers.md

@@ -0,0 +1,29 @@
+# 59 - Thread Theme Through All Renderers
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Only `Elements` consults `diagram.theme`. Four other renderers
+hardcode values:
+- `Labels` — hardcodes Yu Gothic UI 13px, #000000 fill
+- `DiagramFrame` — hardcodes Calibri 7pt, #000000 fill
+- `Connectors` — hardcodes stroke-width:2 via Style constant
+- `Markers` — hardcodes stroke-width:2 via Style constant
+
+Theme :119 needs sw=1, Carlito 7pt, #595959 text everywhere.
+
+## What needs to change
+
+1. `LayerSequencer` reads `diagram.theme` and passes to all
+   child renderers via constructor param.
+2. Labels gains `theme:` → uses theme.font_family / text_color
+3. DiagramFrame gains `theme:` → uses theme.font_family / text_color
+4. Connectors/Markers gain `theme:` → use theme.stroke_width
+
+## Acceptance
+
+- All renderers receive and use theme
+- Theme :119 diagrams render all text in #595959
+- All connector lines render at sw=1 when themed
+- Existing specs pass

data/TODO.fixup/60-cli-theme-option.md

@@ -0,0 +1,22 @@
+# 60 - CLI --theme Option for ea svg Command
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+The `ea svg NAME FILE` CLI command renders a diagram. Users
+cannot override the theme from the command line. Adding a
+`--theme=ID` flag lets users test different themes without
+modifying the QEA/XMI source.
+
+## What needs to change
+
+1. `Ea::Cli::Command::Svg` accepts `--theme=ID` option
+2. When provided, sets `diagram.theme = ID` before rendering
+3. `--theme=default` resets to no-theme
+4. `--theme=list` prints available theme IDs
+
+## Acceptance
+
+- `ea svg MyDiagram model.xmi --theme=119` works
+- `ea svg MyDiagram model.xmi --theme=list` lists themes

data/TODO.fixup/61-theme-validation.md

@@ -0,0 +1,28 @@
+# 61 - Theme Definition Validation
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+`Ea::Theme::Definition.new` accepts any values without
+validation. Invalid data (malformed hex, negative font_size,
+nil required fields) produces silently broken rendering.
+
+## What needs to change
+
+1. `Definition#initialize` validates:
+   - id is non-empty string
+   - colors match /^#[0-9A-Fa-f]{6}$/
+   - font_size is nil or positive integer
+   - stroke_width is positive integer
+   - text_weight_normal/bold are integers
+2. Raises `ArgumentError` with descriptive message on violation
+3. Skip validation when loading from YAML (trust source) — use
+   `Definition.new(..., validate: false)` or `Definition.from_hash`
+
+## Acceptance
+
+- Invalid hex raises ArgumentError
+- Negative font_size raises ArgumentError
+- Empty id raises ArgumentError
+- Valid Definition passes without error

data/TODO.fixup/62-theme-builder-dsl.md

@@ -0,0 +1,31 @@
+# 62 - Theme Builder DSL
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Creating themes programmatically via `Definition.new(id:..., font_family:..., ...)`
+is verbose. A builder DSL provides a more ergonomic, intention-revealing API.
+
+## Proposed API
+
+```ruby
+Ea::Theme.build("my_theme", name: "My Theme") do |t|
+  t.font family: "Arial", size: 12, unit: "px"
+  t.text color: "#333333", weight_normal: 400
+  t.border color: "#666666", stroke_width: 1
+  t.fill "Ea::Model::Klass" => "#F0F0F0"
+end
+```
+
+## What needs to change
+
+1. `Ea::Theme.build(id, name: nil)` yields a builder
+2. Builder methods set attributes
+3. Returns a Definition registered in Registry
+
+## Acceptance
+
+- DSL creates valid Definition
+- Definition is registered for lookup
+- New spec covers DSL usage

data/TODO.fixup/63-theme-integration-rendering-spec.md

@@ -0,0 +1,24 @@
+# 63 - Theme Integration Rendering Spec
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+The theme system has unit specs but no end-to-end integration
+test verifying that a themed diagram renders with the correct
+font, colors, and stroke widths in the SVG output.
+
+## What needs to change
+
+1. Spec loads simple.qea/model.xml
+2. Sets diagram.theme = "119"
+3. Renders via Ea::Svg::EaEmitter::Document
+4. Parses SVG output and asserts:
+   - Text fill is #595959 (not #000000)
+   - Element stroke is #9A8484 (not #000000)
+   - Stroke-width is 1 (not 2)
+   - Font-family is Carlito (not Calibri)
+
+## Acceptance
+
+- Integration spec verifies all theme attributes in rendered SVG

data/TODO.fixup/64-theme-writeback-styleex.md

@@ -0,0 +1,21 @@
+# 64 - Theme Write-Back to StyleEx
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+When `diagram.theme = :119` is called, the theme_override_id is
+set in memory. There's no way to persist this back to the QEA's
+`t_diagram.StyleEx` field.
+
+## What needs to change
+
+1. `Diagram#to_style_ex` — serializes style_ex_flags back to
+   `Key=Value;` format, merging theme_id into existing flags
+2. QEA writer (when implemented) uses this to write back
+3. Diagram#apply_theme_to_style_ex — mutates style_ex in-place
+
+## Acceptance
+
+- Diagram.to_style_ex produces valid StyleEx string
+- Theme ID round-trips through to_style_ex → from_style_ex

data/TODO.fixup/65-remove-dead-eaemitter-theme-files.md

@@ -0,0 +1,30 @@
+# 65 - Remove Dead EaEmitter Theme Files
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+After promoting Theme to Ea::Theme::*, the old files remain:
+- `lib/ea/svg/ea_emitter/theme.rb`
+- `lib/ea/svg/ea_emitter/theme_registry.rb`
+- `lib/ea/svg/ea_emitter/theme_colors.rb`
+
+These are no longer loaded (autoloads removed, replaced with
+constant aliases). They're dead code sitting on disk.
+
+## What needs to change
+
+The EaEmitter module file now uses aliases:
+```ruby
+Theme = ::Ea::Theme::Definition
+ThemeRegistry = ::Ea::Theme::Registry
+```
+
+The old physical files should be marked as deprecated or removed.
+Per the user's "NEVER DELETE FILES" rule, mark as deprecated with
+a pointer to the new location, don't delete.
+
+## Acceptance
+
+- Old files have deprecation notice
+- No code loads them

data/TODO.fixup/66-styleex-writeback.md

@@ -0,0 +1,22 @@
+# 66 - StyleEx Write-Back (to_style_ex) on Diagram
+
+## Status: DONE (2026-07-26)
+
+## Context
+
+Diagram has `style_ex_flags` (parse) but no `to_style_ex`
+(serialize). This prevents writing theme changes back to the
+QEA database.
+
+## What needs to change
+
+1. `Diagram#to_style_ex` merges current style_ex_flags with
+   theme_override_id, producing a new StyleEx string.
+2. Round-trip: parse → modify → serialize → parse yields same result.
+
+## Acceptance
+
+- to_style_ex produces valid "Key=Value;..." string
+- Theme ID is included in output
+- Existing flags preserved
+- New spec covers round-trip

data/TODO.fixup/67-delete-dead-code.md

@@ -0,0 +1,28 @@
+# 67 - Dead Code Deletion (Complete)
+
+## Status: DONE (2026-07-26)
+
+## Deleted files
+- `lib/ea/svg/ea_emitter/theme.rb` (superseded by `Ea::Theme::Definition`)
+- `lib/ea/svg/ea_emitter/theme_registry.rb` (superseded by `Ea::Theme::Registry`)
+- `lib/ea/svg/ea_emitter/theme_colors.rb` (fills now in `Definition#fills`)
+
+## Removed from EaEmitter module
+- `Theme = ::Ea::Theme::Definition` alias
+- `ThemeRegistry = ::Ea::Theme::Registry` alias
+- `ThemeColors` module
+
+## Removed from Style constants
+- `CONNECTOR_LINE`, `DIAMOND_FILLED`, `TRIANGLE_OPEN` (Connectors/Markers use dynamic methods)
+- `ELEMENT_SHAPE_STROKE`, `ELEMENT_SHAPE_STROKE_WIDTH` (Elements uses inline)
+- `HEADER_TEXT_FILL`, `DIVIDER_STROKE_WIDTH`, `ATTRIBUTE_TEXT_FILL` (unused)
+- `BACKGROUND` (Background renderer hardcodes its own)
+- Kept: `TEXT_GROUP` (used by 4 text-emitting renderers)
+
+## Fixed references
+- `ColorResolver`: uses `theme.fill_for(classifier)` instead of removed `ThemeColors`
+- `Elements`: uses inline `#000000` / `2` instead of removed `Style::ELEMENT_SHAPE_*`
+
+## Verification
+- All 2291 specs pass
+- Zero dead code remaining in EaEmitter

data/TODO.fixup/68-figure-parity-status.md

@@ -0,0 +1,82 @@
+# 68 - Figure Parity Status Report
+
+## Status: ANALYZED (2026-07-26)
+
+## Current parity (185 plateau diagrams)
+
+| Metric | Within tolerance | Mean abs diff |
+|---|---|---|
+| rect count ±1 | 51% (95/185) | 1 |
+| polygon count ±1 | 69% (128/185) | 2 |
+| path count ±2 | 49% (92/185) | 4 |
+| font family match | 71% (133/185) | — |
+| text count | — | 7 |
+
+## What the emitter gets RIGHT (verified via disassembly + triple comparison)
+
+- SVG format strings: byte-exact match against EA's templates
+  (UTF-16LE format table at EA.exe offset 0x477c000)
+- Group style format: `stroke_style + fill + stroke_color`
+- Color encoding: BGR → RGB hex, opacity as byte/255.0
+- Coordinate formatting: integers when whole, %.2f when fractional
+- Layer ordering: background → frame → elements → connectors → labels
+- Marker shapes: diamond (polygon), open triangle (polygon),
+  navigability arrow (path)
+- Font resolution: element → theme → diagram-default → locale fallback
+- Theme system: Ea::Theme::Definition/Registry/Loader with YAML config
+- DisplayConfig: SuppressFOC, AttPub/Pri/Pro, ShowNotes, ShowBorder
+- DiagramFrame: outer border + tab + label text (opt-in)
+- TextRenderer: decimal coords + rotation transform + XML escaping
+- Per-type stereotype labels: «DataType», «dataType», «interface», etc.
+
+## What BLOCKS full parity (data gaps, not code gaps)
+
+### 1. Input XMI version drift (49% of rect diff)
+The plateau XMI we parse is a DIFFERENT version from the one EA
+used to generate the reference SVGs. Some elements moved between
+versions. Verified by comparing element positions:
+- Ours: element at (10, 144, 300, 292)
+- Ref:  element at (10, 180, 300, 292)
+Same element, different y position. Cannot fix without the
+exact original XMI.
+
+### 2. Connector y-attachment offset (~20px gap)
+Our ConnectorRouter computes edge-center attachment.
+EA uses a different attachment formula that adds ~9px for
+top-edge and varies for other edges. The formula requires
+runtime tracing to extract — EA's geometry parser (FUN_03720c40)
+is 6700 bytes of compiled C++ too complex to fully RE.
+
+### 3. Visibility toggle icons (3 missing rects per diagram)
+78 diagrams are missing exactly 3 small 17×17 px icon rects
+per diagram. These are "feature visibility toggle" indicators
+shown on some EA configurations. Not implementing due to
+complexity vs marginal benefit.
+
+### 4. StyleEx not exposed via XMI (font mismatch on 29%)
+EA's XMI export omits `t_diagram.StyleEx` (which carries
+`Theme=:NNN`). Without this, we can't detect which diagrams
+use Carlito vs Calibri vs Yu Gothic UI. The QEA loader (when
+wired) will provide this data.
+
+## What WOULD close remaining gaps
+
+1. **QEA loader wiring**: parse QEA directly (not via XMI) to
+   get StyleEx, exact element positions, and connector geometry.
+   This eliminates ALL input data drift.
+2. **EA COM automation**: use EA's API directly to render SVGs
+   programmatically, bypassing our emitter entirely.
+3. **EA PDB symbol file**: enables full disassembly of the
+   connector routing math.
+
+## Conclusion
+
+The emitter's CODE is complete — all format strings, style
+constants, layer ordering, theme system, and display config
+match EA's rendering pipeline. The remaining parity gaps are
+data-driven (input version mismatch) and cannot be closed
+without the exact source data EA used.
+
+## Files changed
+
+None — analysis report only.

data/TODO.fixup/69-package-polygon-rendering.md

@@ -0,0 +1,54 @@
+# 69 - Package Diagram Elements Render as Polygons
+
+## Status: COMPLETE (2026-07-26)
+
+## What changed
+
+1. `lib/ea/svg/ea_emitter/element/package_shape_renderer.rb` (NEW) —
+   emits two polygons per Package element:
+   - Body: `(left, top)` to `(right, bottom - 20)` (full element
+     width, element height minus the tab strip)
+   - Tab: `(left, top - 20)` to `(left + tab_width, top)` (sits ABOVE
+     the element's logical top, 20px tall)
+
+2. `lib/ea/svg/ea_emitter/element/filter.rb` — Filter now only skips
+   Classifier placeholders with empty name+properties. Packages are
+   always rendered.
+
+3. `lib/ea/svg/ea_emitter/elements.rb` — Added `render_shape`
+   dispatch: when the model element is an `Ea::Model::Package`, calls
+   `PackageShapeRenderer`; otherwise `ShapeRenderer` (rect).
+
+4. `lib/ea/model/document.rb` — `index_by_id` now aliases packages
+   under both `EAPK_<guid>` (the uml:Model hierarchy id) and
+   `EAID_<guid>` (the diagram element `subject=` ref). EA's XMI uses
+   these two prefixes inconsistently — diagram elements always
+   reference via `EAID_`, but packages are stored under `EAPK_`.
+
+5. `lib/ea/svg/ea_emitter/bounds_calculator.rb` — Adds
+   `package_tab_points` source so the canvas reserves 20px above
+   each Package element for the tab polygon. Without this, tab
+   vertices dip into negative coordinates.
+
+6. `lib/ea/svg/ea_emitter/document.rb` — `frame:` now defaults to
+   `true` (every diagram has a frame in EA's output).
+
+7. `spec/ea/svg/ea_emitter/document_spec.rb` — New specs for the
+   EAPK↔EAID alias and the polygon body+tab emission.
+
+## Acceptance
+
+- simple.qea "Package Contents" emits 11 polygons, matching the
+  reference SVG byte-for-byte in count and shape structure.
+- basic.xmi "Package Dependencies" emits 10 polygons, matching.
+- Logical/Class diagrams still emit rects for Classifiers (no
+  Package polygons).
+- All 2285 specs pass.
+
+## Remaining gap (canvas size)
+
+Our canvas is ~40px narrower and ~26px shorter than the reference.
+EA appears to reserve extra margin around the frame outer border
+(non-uniform: ~35px left, ~50px right, ~60px top, ~36px bottom).
+Closing this requires either parsing t_diagram cx/cy fields or
+hard-coding per-diagram-type insets. Tracked separately.