# 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.
