@jterrats/open-orchestra 1.0.2 → 1.0.3

package/docs/diagrams/state-uml-recreated.prompt.v14.md

@@ -0,0 +1,91 @@
+# Prompt Version 14: Universal Diagram Acceptance Delta
+
+Use this as a delta over the master diagram-generation prompt and later prompt
+versions. This version defines generic acceptance rules that apply to every
+generated diagram: architecture, workflow, state, sequence, infrastructure,
+story maps, and recreated diagrams.
+
+## Append Lines
+
+- Before accepting any rendered diagram, run a whole-canvas acceptance matrix:
+  labels, connectors, containers, long text, z-order, whitespace, and page
+  bounds must all pass together.
+- Treat label-to-label collisions as failures. Labels need visible separation
+  from adjacent labels, connector strokes, arrowheads, symbols, cards, and
+  container borders.
+- Do not use label backgrounds as a visual patch. A label background must not
+  cover, interrupt, hide, or visually erase the connector it describes. If a
+  background hides a stroke, move the label to a clear lane or reroute the
+  connector.
+- Reserve connector label lanes before final routing. When labels compete for a
+  lane, assign separate lanes or move connected elements before adding
+  unnecessary bends.
+- Long text must be layout-managed. Re-evaluate wrapping, line count, width, and
+  placement for every note, annotation, card title, legend item, and connector
+  label. Split text or reposition it when it crosses a connector, touches a
+  border, crowds another element, or invades a neighboring container.
+- Text inside bounded elements must fit inside its own shape. This applies to
+  cards, chips, badges, pills, labels, legends, swimlane headers, callouts, and
+  connector-label boxes. If text grows beyond the available width, wraps poorly,
+  overlaps another element, or visually escapes its shape, split it into
+  multiple lines, grow the containing shape, or move the element before
+  accepting the render.
+- Re-evaluate every bounded text element after wrapping. A wrapped label is only
+  valid if the resulting height still fits with padding and does not collide
+  with connectors, nearby labels, child nodes, or parent boundaries.
+- Treat text wrapping as a geometry change, not as a text-only fix. After any
+  label, pill, badge, note, callout, or card text wraps to more lines,
+  recalculate the rendered bounding box and move the element before accepting
+  the render. The expanded box must not cover the connector, border, or element
+  it previously cleared.
+- A connector label must clear the whole connector stroke after final wrapping,
+  including the label background and padding. If a two-line label overlaps the
+  stroke, arrowhead, or crossing point, move the label to a new lane or reroute
+  the connector.
+- Prefer the simplest readable connector route. Use a straight line when the
+  source and target have clear line-of-sight; use one orthogonal bend when it
+  improves readability; use curves, multi-bend routes, or jumps only when they
+  avoid a real obstacle or crossing.
+- Before keeping a curved connector, verify that a straight or orthogonal route
+  would collide with an element, label, boundary, or reserved lane. If no
+  collision exists, replace the curve with the simpler route.
+- Connector intent must determine the endpoint. A connector targeting a group or
+  boundary stops at that boundary edge; a connector targeting a child element
+  must visibly attach to that child. Do not let connectors drift inside a
+  container unless the interior target is intentional and unambiguous.
+- Validate parent containment using actual rendered bounds, not intended bounds.
+  Containers, swimlanes, groups, frames, and regions must contain all visible
+  children with padding after real labels, badges, notes, icons, internal
+  connectors, and arrowheads are placed.
+- If any child element touches, crosses, or visually crowds its parent boundary,
+  grow the parent, move the child, or reflow neighboring regions. Do not accept
+  clipping or overflow as a styling choice.
+- Re-render after every containment, wrapping, lane, or endpoint correction, then
+  inspect the whole canvas again. A local fix is incomplete until no new
+  collisions, hidden endpoints, or containment failures appear elsewhere.
+- A regenerated version must change geometry when it is meant to fix a visual
+  finding. If the same collision, overflow, endpoint gap, or connector route
+  persists across versions, stop re-rendering and change the layout strategy:
+  move elements, grow containers, reserve a different lane, or reroute the
+  connector.
+
+## Validation Additions
+
+- Record whether labels collide with other labels, connectors, arrowheads,
+  borders, cards, or notes.
+- Record whether long text was wrapped, resized by container growth, moved, or
+  accepted as-is.
+- Record whether bounded text elements fit inside their own shapes after final
+  wrapping and sizing.
+- Record whether every wrapped bounded text element was repositioned or
+  revalidated against the connector lanes it may now occupy.
+- Record whether each curved or multi-bend connector has a concrete obstacle
+  reason. If not, simplify the route before handoff.
+- Record whether every connector endpoint matches its semantic target:
+  boundary, child node, symbol, lane, or external element.
+- Record whether every parent container contains all visible children after
+  final sizing and reflow.
+- Record which geometry changed between render passes for every accepted visual
+  correction. A version number without geometry change is not a valid fix.
+- Record the final render pass number and the remaining known visual risks, if
+  any.

package/docs/diagrams/state-uml-recreated.prompt.v2.md

@@ -0,0 +1,31 @@
+# Prompt Version 2: UML State Diagram Visual Correction Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the first rendered
+SVG/draw.io pass.
+
+## Append Lines
+
+- Re-evaluate every container after rendering, because labels may make boxes too
+  short or visually unbalanced once the diagram is assembled.
+- Prefer connector bend points that keep arrows outside containers and labels.
+- Avoid vertical connector stubs when a small horizontal or orthogonal route reads
+  closer to the source diagram.
+- Reposition arrowheads so they land on the intended shape boundary instead of
+  appearing deep inside the target container.
+- Re-check spacing after resizing containers; container growth must not create
+  new overlaps or unclear routes.
+
+## Modify Lines
+
+- Change `connector routing and bend points` to `connector routing, bend points,
+and post-render adjustment against the source reference`.
+- Change `final resizing after the diagram is assembled` to `final resizing and
+visual balance pass after the diagram is assembled and rendered`.
+
+## Validation Additions
+
+- Inspect the browser-rendered SVG screenshot before handoff.
+- Compare each connector against the source PDF page and identify whether it
+  connects to the expected source and target element.
+- Record any remaining approximation if the recreated diagram is not
+  pixel-perfect.

package/docs/diagrams/state-uml-recreated.prompt.v3.md

@@ -0,0 +1,36 @@
+# Prompt Version 3: UML State Diagram Endpoint and Rotation Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the second
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Validate endpoint distance from source to target, so every connector visibly
+  touches both the origin and destination edges.
+- For each connector, confirm the line starts at the visual boundary of the
+  source element and ends at the visual boundary of the intended target element.
+- If a label such as `Radio`, `CD`, `on`, or `off` implies a specific target
+  state, the arrow must reach that state instead of stopping at the parent
+  container.
+- Route arrows so they do not cover state labels or transition labels unless the
+  source diagram explicitly does so.
+- Preserve rotated labels from the source diagram. When the source uses Lucid
+  style rotation values such as `270` or `-90`, map the same intent into draw.io
+  with `rotation=<degrees>` for rotated cells or `textRotation=<degrees>` when
+  only the label axis should rotate.
+
+## Modify Lines
+
+- Change `arrows terminating at the intended connection edge, not deep inside
+shapes` to `arrows visibly starting at the source edge and terminating at the
+intended target edge, not floating near shapes or ending deep inside them`.
+- Change `typography, label placement, and text wrapping` to `typography, label
+placement, text wrapping, and source-matched text rotation`.
+
+## Validation Additions
+
+- Perform a connector-by-connector source-to-target audit on the rendered
+  screenshot.
+- Verify each transition label maps to the element it semantically references.
+- Verify vertical or diagonal labels use explicit rotation values instead of
+  simulated line breaks or spacing.

package/docs/diagrams/state-uml-recreated.prompt.v4.md

@@ -0,0 +1,35 @@
+# Prompt Version 4: UML State Diagram Label Clearance Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the third
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Validate label boundary clearance after rendering: every label needs a visible
+  margin from container borders, connector lines, and arrowheads.
+- Labels must not sit directly on a shape boundary unless the source diagram
+  explicitly requires that overlap.
+- Reposition transition labels that land on a container border after rendering.
+- When edge labels cannot be positioned cleanly by the diagram tool, model them
+  as independent text elements so their placement can be controlled precisely.
+- After every visual correction, re-render the SVG and inspect the screenshot
+  again before handoff.
+
+## Modify Lines
+
+- Change `connector label avoidance: route arrows so they do not cover state
+labels or transition labels unless the source diagram explicitly does so` to
+  `connector and label clearance: route arrows and labels so neither labels nor
+connector lines sit on shape borders, arrowheads, or important text unless the
+source diagram explicitly does so`.
+- Change `final resizing and visual balance pass after the diagram is assembled
+and rendered` to `final resizing, label clearance, and visual balance pass
+after each render-correction cycle`.
+
+## Validation Additions
+
+- Inspect each label against its nearest container border after rendering.
+- Re-render after moving labels and compare the screenshot before treating the
+  diagram as ready.
+- Record the correction if a label had to become an independent text element to
+  avoid edge-label placement issues.

package/docs/diagrams/state-uml-recreated.prompt.v5.md

@@ -0,0 +1,35 @@
+# Prompt Version 5: UML State Diagram Element Ordering Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the fourth
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Validate element ordering and z-index after rendering.
+- Draw large containers and state shapes first, then draw the connector lines
+  that connect them, then draw labels and annotations that must stay readable.
+- A connector must not be hidden behind the element it connects. If the
+  arrowhead or endpoint disappears under the target element, reorder the element
+  layers or move the endpoint to the visible boundary.
+- Preserve diagrams that already passed visual QA. When regenerating all
+  diagrams, do not regress previously accepted sections such as the v4
+  concurrent state diagram.
+- Re-render the full SVG after z-order corrections and inspect every diagram,
+  not just the section that changed.
+
+## Modify Lines
+
+- Change `final resizing, label clearance, and visual balance pass after each
+render-correction cycle` to `final resizing, label clearance, z-order, and
+visual balance pass after each render-correction cycle`.
+- Change `Visual endpoint QA for every connector in the rendered screenshot` to
+  `Visual endpoint and z-order QA for every connector in the rendered
+screenshot`.
+
+## Validation Additions
+
+- Check every arrowhead against the target element boundary.
+- Check every line segment that enters a connected element; it must remain
+  visible until the intended boundary point.
+- If a shape overlaps a connector, decide whether the overlap is intentional. If
+  not intentional, fix the layer order, bend points, or endpoint.

package/docs/diagrams/state-uml-recreated.prompt.v6.md

@@ -0,0 +1,39 @@
+# Prompt Version 6: UML State Diagram Connector Anchor Aesthetics Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the fifth
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Validate connector anchor-point aesthetics after rendering.
+- Choose the source edge and target edge that create the shortest readable
+  orthogonal path with the fewest bend points.
+- Prefer side midpoints when a side connection avoids extra turns that would be
+  required by a top or bottom connection.
+- Do not force a connector to start from a top or bottom edge when the left or
+  right side of the source element produces a cleaner route.
+- When two connector options both preserve semantic correctness, choose the one
+  with fewer 90-degree bends and less line travel.
+- Arrowheads should land on a clean boundary point, commonly the midpoint of the
+  relevant side, without entering the target element interior.
+- Re-render after anchor changes and verify the result against all previous
+  quality gates: endpoint, label clearance, z-order, text rotation, and
+  container overlap.
+
+## Modify Lines
+
+- Change `connector routing, bend points, and post-render adjustment against the
+source reference` to `connector routing, source/target anchor choice, bend
+points, and post-render adjustment against the source reference`.
+- Change `Visual endpoint and z-order QA for every connector in the rendered
+screenshot` to `Visual endpoint, anchor-point, and z-order QA for every
+connector in the rendered screenshot`.
+
+## Validation Additions
+
+- Count bend points for each connector and compare against a cleaner route from
+  another edge.
+- Check whether moving the source point to the nearest side midpoint reduces
+  bends without changing the semantic target.
+- Check whether the target arrowhead lands at a side midpoint or other clean
+  boundary point instead of a corner or shape interior.

package/docs/diagrams/state-uml-recreated.prompt.v7.md

@@ -0,0 +1,37 @@
+# Prompt Version 7: UML State Diagram Orthogonal Lines and Crossing Jumps Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the sixth
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Avoid diagonal connectors whenever an orthogonal route can preserve the same
+  semantic relationship.
+- Prefer horizontal and vertical connector segments with explicit bend points
+  over diagonal connector segments.
+- If two lines must cross, add a visible bridge or jump on the line that passes
+  over the other line.
+- In SVG, represent line jumps with a small curve or arc at the crossing point.
+- In draw.io, prefer editable line jump styles such as `jumpStyle=arc` and a
+  small jump size.
+- Preserve accepted diagram sections unless the new orthogonal/crossing rule
+  identifies an actual visual defect.
+
+## Modify Lines
+
+- Change `connector routing, source/target anchor choice, bend points, and
+post-render adjustment against the source reference` to `orthogonal connector
+routing, source/target anchor choice, bend points, crossing jumps, and
+post-render adjustment against the source reference`.
+- Change `Visual endpoint, anchor-point, and z-order QA for every connector` to
+  `Visual endpoint, anchor-point, z-order, diagonal, and crossing QA for every
+connector`.
+
+## Validation Additions
+
+- Inspect Shallow History and Entry/Exit Actions for diagonal connectors and
+  convert them to orthogonal routes where practical.
+- Inspect every line intersection; if the crossing is unavoidable, add a
+  jump/bridge rather than allowing the two lines to visually merge.
+- Re-render after orthogonal and crossing corrections, then verify no previous
+  accepted diagram section regressed.

package/docs/diagrams/state-uml-recreated.prompt.v8.md

@@ -0,0 +1,41 @@
+# Prompt Version 8: UML State Diagram Layout Simplification Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the seventh
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Before accepting a connector bend, re-evaluate the positions of both connected
+  elements.
+- If moving the source or target element slightly can remove a bend without
+  changing the meaning of the diagram, prefer the repositioned layout.
+- Do not optimize a single connector at the cost of making surrounding
+  connectors worse; re-render and inspect the local neighborhood after moving an
+  element.
+- Prefer aligned centers when a state and decision/gateway are conceptually
+  connected vertically.
+- Keep editable draw.io XML and rendered SVG geometrically equivalent. If an
+  element, connector, label, or annotation moves in the SVG, the draw.io source
+  must carry the corresponding editable cell or edge.
+- Preserve accepted sections unless the layout simplification reveals a concrete
+  visual defect.
+
+## Modify Lines
+
+- Change `connector routing, source/target anchor choice, bend points, and
+post-render adjustment against the source reference` to `connector routing,
+element positioning, source/target anchor choice, bend points, and post-render
+adjustment against the source reference`.
+- Change `Visual anchor-point QA for every connector` to `Visual anchor-point and
+element-position QA for every connector`.
+
+## Validation Additions
+
+- For every connector with a bend, ask whether moving either connected element
+  could reduce the bend count.
+- Verify the move does not introduce new overlaps, label collisions, hidden
+  endpoints, or additional bends elsewhere.
+- Verify the draw.io XML contains the same moved elements, connectors, labels,
+  and annotations as the rendered SVG.
+- Re-render after the repositioning and compare the local section against the
+  previous accepted render.

package/docs/diagrams/state-uml-recreated.prompt.v9.md

@@ -0,0 +1,32 @@
+# Prompt Version 9: UML Annotation Target Clarity Delta
+
+Use this as a delta over `state-uml-recreated.prompt.md` after the eighth
+rendered SVG/draw.io pass.
+
+## Append Lines
+
+- Every annotation arrow must have an explicit visual target. The arrowhead
+  should land on the annotated element boundary or on the specific line segment
+  being described.
+- Annotation arrows must not disappear behind the element they annotate.
+- Annotation labels must not cover state names, action text, connector labels,
+  or connector lines.
+- If an annotation points to a state-internal action, prefer a direct vertical or
+  horizontal pointer and move the label to create enough room.
+- If an annotation points to a transition line, place the arrowhead near the
+  line without hiding the line's semantic direction.
+- Keep annotation labels and annotation arrows editable in draw.io when they are
+  present in the rendered SVG.
+
+## Modify Lines
+
+- Change `label boundary clearance` to include annotation labels and annotation
+  arrows, not only state and transition labels.
+- Change `editable/rendered equivalence` to require red annotation text and red
+  annotation arrows as editable draw.io cells when present in SVG.
+
+## Validation Additions
+
+- For every red annotation, answer: what exact element or line does it annotate?
+- Verify the arrowhead visibly reaches that exact target.
+- Verify annotation labels do not obscure the target text or connector label.

package/docs/diagrams/state-uml-recreated.svg

@@ -0,0 +1,159 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1180" height="1680" viewBox="0 0 1180 1680" role="img" aria-labelledby="title desc">
+  <title id="title">Recreated UML state diagram examples from downloaded PDF</title>
+  <desc id="desc">Three UML state diagram examples recreated as vector SVG: concurrent state, shallow history state, and entry exit action notation.</desc>
+  <defs>
+    <marker id="arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto" markerUnits="strokeWidth">
+      <path d="M0,0 L0,6 L9,3 z" fill="#222222" />
+    </marker>
+    <marker id="red-arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto" markerUnits="strokeWidth">
+      <path d="M0,0 L0,6 L9,3 z" fill="#e35c5c" />
+    </marker>
+    <style>
+      .panel { fill: #74c7ed; stroke: #222222; stroke-width: 2; }
+      .state { fill: #74c7ed; stroke: #222222; stroke-width: 2; }
+      .line { fill: none; stroke: #222222; stroke-width: 2; marker-end: url(#arrow); }
+      .plain-line { fill: none; stroke: #222222; stroke-width: 2; }
+      .region-line { stroke: #222222; stroke-width: 2; stroke-dasharray: 8 5; }
+      .label { font-family: Arial, Helvetica, sans-serif; font-size: 18px; fill: #1f2933; }
+      .small { font-family: Arial, Helvetica, sans-serif; font-size: 15px; fill: #1f2933; }
+      .tiny { font-family: Arial, Helvetica, sans-serif; font-size: 13px; fill: #1f2933; }
+      .red { font-family: Arial, Helvetica, sans-serif; font-weight: 700; font-size: 20px; fill: #e35c5c; }
+      .redline { fill: none; stroke: #e35c5c; stroke-width: 3; stroke-dasharray: 10 8; marker-end: url(#red-arrow); }
+      .section-title { font-family: Arial, Helvetica, sans-serif; font-weight: 700; font-size: 24px; fill: #1f2933; }
+    </style>
+  </defs>
+
+  <rect x="0" y="0" width="1180" height="1680" fill="#ffffff" />
+
+  <text x="40" y="44" class="section-title">Estado concurrente</text>
+  <g transform="translate(70 76)">
+    <rect x="110" y="0" width="500" height="360" rx="12" class="panel" />
+    <text x="360" y="18" text-anchor="middle" class="small">On</text>
+    <line x1="110" y1="120" x2="610" y2="120" class="plain-line" />
+    <line x1="110" y1="190" x2="610" y2="190" class="region-line" />
+
+    <rect x="190" y="88" width="150" height="62" rx="12" class="state" />
+    <text x="265" y="113" text-anchor="middle" class="small">Display Current</text>
+    <text x="265" y="136" text-anchor="middle" class="small">Time</text>
+
+    <rect x="370" y="88" width="150" height="62" rx="12" class="state" />
+    <text x="445" y="113" text-anchor="middle" class="small">Display Alarm</text>
+    <text x="445" y="136" text-anchor="middle" class="small">Time</text>
+
+    <path d="M110 120 H190" class="line" />
+    <text x="132" y="112" class="small">time</text>
+    <path d="M610 120 H520" class="line" />
+    <text x="548" y="112" class="small">alarm</text>
+
+    <circle cx="148" cy="270" r="14" fill="#74c7ed" stroke="#222222" stroke-width="2" />
+    <text x="148" y="276" text-anchor="middle" class="small">H</text>
+    <path d="M162 270 H220" class="line" />
+
+    <rect x="220" y="240" width="120" height="62" rx="12" class="state" />
+    <text x="280" y="265" text-anchor="middle" class="small">Playing Radio</text>
+
+    <rect x="370" y="240" width="120" height="62" rx="12" class="state" />
+    <text x="430" y="265" text-anchor="middle" class="small">Playing CD</text>
+
+    <path d="M292 469 H280 V302" class="line" />
+    <text x="286" y="338" class="label">Radio</text>
+    <path d="M392 438 V404 H430 V302" class="line" />
+    <text x="448" y="338" class="label">CD</text>
+
+    <rect x="292" y="438" width="170" height="62" rx="12" class="state" />
+    <text x="377" y="474" text-anchor="middle" class="label">Off</text>
+    <path d="M356 438 V360" class="line" />
+    <text x="368" y="414" class="small">on</text>
+    <path d="M462 360 V438" class="line" />
+    <text x="472" y="414" class="small">off</text>
+  </g>
+
+  <text x="40" y="650" class="section-title">Shallow history state</text>
+  <g transform="translate(60 685)">
+    <text x="98" y="34" class="red">State</text>
+    <path d="M130 48 V92" class="redline" />
+    <text x="245" y="-12" class="red">Shallow History State</text>
+    <path d="M365 0 V107" class="redline" />
+
+    <rect x="75" y="95" width="120" height="60" rx="10" class="state" />
+    <text x="135" y="130" text-anchor="middle" class="small">Command</text>
+    <rect x="330" y="48" width="290" height="350" rx="12" class="panel" />
+    <text x="475" y="66" text-anchor="middle" class="small">BackingUp</text>
+
+    <circle cx="370" cy="122" r="15" fill="#74c7ed" stroke="#222222" stroke-width="2" />
+    <text x="370" y="128" text-anchor="middle" class="small">H</text>
+    <rect x="455" y="95" width="120" height="60" rx="10" class="state" />
+    <text x="515" y="130" text-anchor="middle" class="small">Collecting</text>
+
+    <rect x="455" y="205" width="120" height="60" rx="10" class="state" />
+    <text x="515" y="240" text-anchor="middle" class="small">Copying</text>
+
+    <rect x="455" y="325" width="120" height="60" rx="10" class="state" />
+    <text x="515" y="360" text-anchor="middle" class="small">Cleaning Up</text>
+
+    <path d="M195 125 H355" class="line" />
+    <path d="M385 122 H455" class="line" />
+    <path d="M515 155 V205" class="line" />
+    <path d="M515 265 V325" class="line" />
+    <path d="M330 205 H150 V155" class="line" />
+    <text x="210" y="196" class="small">query</text>
+    <path d="M455 355 H120 V155" class="line" />
+
+    <text x="180" y="415" class="red">Transition</text>
+    <path d="M232 395 V366 C232 359 244 359 244 355 C244 351 232 351 232 344 V322" class="redline" />
+  </g>
+
+  <text x="40" y="1130" class="section-title">Acciones de entrada y salida</text>
+  <g transform="translate(55 1160)">
+    <text x="190" y="28" class="red">Initial Pseudo State</text>
+    <circle cx="430" cy="42" r="12" fill="#000000" />
+
+    <rect x="350" y="125" width="190" height="92" rx="10" class="state" />
+    <text x="445" y="144" text-anchor="middle" class="tiny">State</text>
+    <line x1="350" y1="150" x2="540" y2="150" class="plain-line" />
+    <text x="363" y="170" class="tiny">entry / Action 1_1</text>
+    <text x="363" y="190" class="tiny">do / Action 1_2</text>
+
+    <rect x="815" y="125" width="190" height="98" rx="10" class="state" />
+    <text x="910" y="144" text-anchor="middle" class="tiny">State2</text>
+    <line x1="815" y1="150" x2="1005" y2="150" class="plain-line" />
+    <text x="828" y="170" class="tiny">entry / Action 2_1</text>
+    <text x="828" y="190" class="tiny">Action 2_3 / defer</text>
+    <text x="828" y="210" class="tiny">exit / Action 2_2</text>
+    <polygon points="445,322 473,338 445,354 417,338" fill="#74c7ed" stroke="#222222" stroke-width="2" />
+    <circle cx="445" cy="438" r="14" fill="#ffffff" stroke="#000000" stroke-width="2" />
+    <circle cx="445" cy="438" r="9" fill="#000000" />
+
+    <rect x="575" y="295" width="190" height="88" rx="10" class="state" />
+    <text x="670" y="338" text-anchor="middle" class="tiny">State2</text>
+    <text x="588" y="354" class="tiny">entry / Action 3_1</text>
+
+    <path d="M430 54 V125" class="line" />
+    <path d="M540 166 H815" class="line" />
+    <text x="575" y="156" class="tiny">event [Guard1] / ActionA</text>
+    <path d="M445 322 V217" class="line" />
+    <text x="470" y="276" class="tiny">[Guard4]</text>
+    <path d="M445 354 V420" class="line" />
+    <text x="458" y="388" class="tiny">[Else]</text>
+    <path d="M815 175 H670 V295" class="line" />
+    <text x="690" y="270" class="tiny">[Guard3] / ActionB</text>
+    <path d="M1005 206 V338 H765" class="line" />
+    <text x="890" y="364" class="tiny">[Guard2]</text>
+    <path d="M575 338 H473" class="line" />
+
+    <text x="18" y="162" class="red">Entry action</text>
+    <path d="M188 158 H350" class="redline" />
+    <text x="268" y="248" class="red">Action in state</text>
+    <path d="M392 236 V198" class="redline" />
+    <text x="240" y="350" class="red">Decision</text>
+    <path d="M330 343 H417" class="redline" />
+    <text x="610" y="58" class="red">Transition</text>
+    <path d="M660 68 V148" class="redline" />
+    <text x="780" y="44" class="red">Triggered Action</text>
+    <path d="M905 54 V158" class="redline" />
+    <text x="1018" y="230" class="red">Exit action</text>
+    <path d="M1014 206 H946" class="redline" />
+    <text x="230" y="444" class="red">Final State</text>
+    <path d="M350 438 H431" class="redline" />
+  </g>
+</svg>

package/docs/diagrams/v14-stress-test/README.md

@@ -0,0 +1,33 @@
+# V14 Diagram Acceptance Stress Test
+
+Task: DIAGRAM-V14-STRESS-TEST
+
+## Purpose
+
+Validate generic v14 diagram rules against a source-free stress diagram with:
+
+- bounded text inside chips, cards, labels, and notes;
+- connector labels placed in clear lanes;
+- parent containers sized around all visible children;
+- boundary-target connectors that stop at container edges;
+- long text split into multiple lines instead of crossing connectors or
+  neighboring containers.
+
+## Expected Visual Result
+
+- No text escapes its own shape.
+- No connector label hides a connector stroke or arrowhead.
+- No two labels overlap each other.
+- The parent containers contain all child cards and labels.
+- The long note is wrapped and placed in whitespace.
+- Boundary connectors terminate at the target boundary edge.
+- Wrapped connector labels remain clear of the connector stroke after their
+  final two-line bounding box is known.
+- Curved or multi-bend connectors are simplified when source and target have
+  clear line-of-sight.
+
+## Current Candidate
+
+Render preview:
+
+`output/diagram-experiments/v14-stress-test/preview-v3.png`