Every read in the section was `border-top-*` answering for the whole box, so
`.header { border-bottom: 1px solid }` showed as unstroked and editing it wrote
to the wrong edge. `edgeValue()` folds all four longhands through `agreed`,
comparing colours with `sameColor` so one colour spelled two ways is not
reported as Mixed.
The eye was a live bug rather than a cosmetic one. Three writes still went
through the `border-style` shorthand, while `hasStroke` reads longhands through
`ctx.gate`, which does no shorthand expansion. A pending longhand `solid`
therefore shadowed a shorthand `none` forever: the eye toggled, the gate kept
reading `solid`, and nothing happened again. All three writes go through
`writeAllEdges` now. `strokeColor` is passed as the colour row's re-seed reader
for the same class of reason — without it the four registered properties push
four `setValue` calls and `border-left-color` wins by arriving last.
`splitBorder` had no first-wins guard on `width`, so `border: 1px solid
var(--border)` let the `var()` overwrite `1px` and left the colour undefined
entirely. The forced-state preview got `border-*-width: var(--border)` and no
colour at all.
First tests for `renderStroke`, covering all six defects, plus a `MixedEdges`
story and the `mixedBorder` specimen it renders.