The rule being demonstrated: the control row is always exactly one row. As the container narrows, controls move into the MORE panel in the order the issue specifies — Status, then Home Type, then Beds/Baths, then Price — carrying their selected values. Widening brings them back. The search input, MORE and VIEW never leave.
Try it: set Beds and a Price on the 1200px rig, then compare the 480px one — open its MORE panel and the moved controls are at the top, still holding your values.
What this page is. It runs a locally built bundle and stylesheet from this site's own
/src/, not the shared preview build. So it shows exactly the candidate change and
cannot be silently overwritten. It is a design-review surface, not release evidence —
it does not exercise the path this ships through.
← the before, same widths (current behaviour: 2 rows at 768, 3 rows at 480 and below, nothing ever moving into MORE).
No menu, no Save Search — those exist only on the results-header mount.
Carries the menu and Save Search. Below a 768px container those two move to a row above, and the control row below stays one row — a separate mechanic from the removals.