Add a per-target "⇄ input" toggle (normal/inverted): an inverted target
follows the opposite of its input (a wired boolean or a Wired Controller
patch signal), so one boolean can drive two targets to opposite states -
the either/or case from issue #1. Inversion only affects input-driven
targets; manually-toggled targets are unaffected.
Add a thin divider line before each target group and after the last one,
so the per-target rows (toggle / disable as / invert) no longer blur into
the next group or into the add/remove controls. Draws on the legacy
canvas; collapses to a small gap under the Nodes 2.0 renderer.
Bump version to 1.1.5. README: "Inverting an input" section with example
screenshot, a precedence-table row, and the divider note.
Oratorian
dec6ae629c
