chore(deps): bump schematex from 1.0.14 to 1.1.2

[dependabot]

Bumps schematex from 1.0.14 to 1.1.2.

Release notes

Sourced from schematex's releases.

v1.1.2

1.1.1 was never published to npm, so 1.1.2 is the first release after 1.1.0 and also ships the 1.1.1 fixes below.

Fixed

• Genogram: a person with three or more unions is laid out correctly. Former partners stand on one side in declaration order and the current partner next to them on the other; every union line touches only its own two partners, and each child descends only from its own parents' union. In 1.1.0 the third union could be drawn between two of the person's other partners, with its children hanging below the wrong person.
• Genogram: a union between partners who are not side by side is routed over the people in between instead of through them, with nested routes for several former unions. A union that ended in a partner's death is ordered with the ended unions and carries no divorce marks.
• Genogram: a former partner's other spouse stands on that partner's far side, and each gap between neighbours carries the descent of one union only, so two couples' children never share a line or a sibling bar.
• Genogram: where a parent's line crosses a routed union, the crossing is drawn as a visible gap rather than a junction, and a routed union's leg never runs along a parent line entering the same person.
• Genogram: a sibling group stays contiguous in birth order, and a person who marries into the family stands on the outer side of their spouse's siblings. In the Potter example the Evans sisters now stand together with their husbands outside, so James and Lily are neighbours and Harry and his cousin Dudley no longer hang from one sibling bar. A person with several unions keeps their siblings outside the whole partner sequence.
• Genogram: after a generation is reordered, each parent couple is placed above its own children, so descent lines drop straight instead of jogging sideways or crossing the chart.
• Genogram: two couples' children never share a sibling bar, and emotional relationship lines never run along another emotional or structural line.
• Genogram: the final spacing pass runs after union reordering, so the change introduces no new symbol or label collisions; on the eval corpus no case has more collisions than 1.1.0 and several have fewer.

Added

• Visual-eval cases for one parent with three unions (mother and father), an ex-partner who remarried, and three unions with parents above, each with a hand-drawn target.
• v1.1.0 snapshots for the eval corpus, rendered with the published schematex@1.1.0, so the review page compares against what ChatDiagram runs.
• scripts/visual-eval/genogram-overlaps.mts --check: counts symbol and label collisions per genogram case for the working tree against the v1.1.0 snapshot.

---

... (truncated)

Changelog

Sourced from schematex's changelog.

[1.1.2] — 2026-10-06

1.1.1 was never published to npm, so 1.1.2 is the first release after 1.1.0 and also ships the 1.1.1 fixes below.

Fixed

• Genogram: a person with three or more unions is laid out correctly. Former partners stand on one side in declaration order and the current partner next to them on the other; every union line touches only its own two partners, and each child descends only from its own parents' union. In 1.1.0 the third union could be drawn between two of the person's other partners, with its children hanging below the wrong person.
• Genogram: a union between partners who are not side by side is routed over the people in between instead of through them, with nested routes for several former unions. A union that ended in a partner's death is ordered with the ended unions and carries no divorce marks.
• Genogram: a former partner's other spouse stands on that partner's far side, and each gap between neighbours carries the descent of one union only, so two couples' children never share a line or a sibling bar.
• Genogram: where a parent's line crosses a routed union, the crossing is drawn as a visible gap rather than a junction, and a routed union's leg never runs along a parent line entering the same person.
• Genogram: a sibling group stays contiguous in birth order, and a person who marries into the family stands on the outer side of their spouse's siblings. In the Potter example the Evans sisters now stand together with their husbands outside, so James and Lily are neighbours and Harry and his cousin Dudley no longer hang from one sibling bar. A person with several unions keeps their siblings outside the whole partner sequence.
• Genogram: after a generation is reordered, each parent couple is placed above its own children, so descent lines drop straight instead of jogging sideways or crossing the chart.
• Genogram: two couples' children never share a sibling bar, and emotional relationship lines never run along another emotional or structural line.
• Genogram: the final spacing pass runs after union reordering, so the change introduces no new symbol or label collisions; on the eval corpus no case has more collisions than 1.1.0 and several have fewer.

Added

• Visual-eval cases for one parent with three unions (mother and father), an ex-partner who remarried, and three unions with parents above, each with a hand-drawn target.
• v1.1.0 snapshots for the eval corpus, rendered with the published schematex@1.1.0, so the review page compares against what ChatDiagram runs.
• scripts/visual-eval/genogram-overlaps.mts --check: counts symbol and label collisions per genogram case for the working tree against the v1.1.0 snapshot.

---

... (truncated)

Commits

• 254bc20 fix(genogram): lay out people with three or more unions (1.1.2) (#124)
• b6cfb82 fix: restore ERD and SLD rendering in 1.1.1 (#123)
• 12965e2 feat(diagrams): refresh engines, symbol library and visual evaluation (#120)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)