The FX row had grown into a flat list where a brush and a filter and a
shape sat side by side, and it lied about what the tools are: HEAL and
MOSAIC only paint, LINEAR and RADIAL only make a mask. The row now
carries FIX and GRADIENT MASK, in that order, before MONOCHROME, and
each one opens its own strip holding the tools that belong to it —
turning amber when it has a spot or a mask to show for itself, so the
state still reads from the row without opening anything.
The two brushes moved into the FIX strip with the header FIX above
them, the two shapes into the GRADIENT MASK strip under the header
GRADIENT MASK, and each CLEAR moved in with the tool it clears instead
of sitting at the end of the row. Opening FIX still arms the brush the
same way — the strip only changes where the chip lives, not what
clicking it does.
The mask column (shine, bearing, feather, and the rest) still hangs off
the shape you pick, so it now stands right after the options column:
the strip that brought it out comes first, then the column it belongs
to. Nothing else in the column order moved.
ponytail: the two strips ride the existing openGroup and toggleGroup, so
a strip key is just a widened GroupKey rather than new state to keep in
sync; the option-strip body itself stayed where it was, keeping the
diff to the chips that moved.
Verified:
- npx tsc --noEmit clean.
- Frontend probes against the built production bundle on :8090 and the
dev server: mask-probe 53/0, brush-edit-probe 35/0, heal-idle-probe
23/0, heal-zoom-drag-probe 28/0, grain-controls 20/0, temp-swatch
33/0, and landing, pro-gate, award-column, otp-code, tone-curve,
hsl-panel, chip-edge, chips-desk, slider-reset all PASS rc=0 fails=0.
- Backend npm test 180/0.
- panel-test keeps exactly its four pre-existing failures (rail labels,
WB swatch); they reproduce on the commit before this one.
3dtours
08a4570b2d