v0.62.0

Five, each small, each the same family as the rest of this week: a thing that
said what was not true, or work nobody could see.

THE SEPARATOR SAYS WHEN IT CANNOT MOVE. Its floor is the conversation's
narrowest and its ceiling is what is left after the picture's, so under a
window about 957px wide the two meet: the ceiling collapses onto the floor.
Below that it was announced to a screen reader with a value, a floor and a
ceiling all equal - a range of zero presented as a range - and to a hand as a
thing you can drag that does nothing. It carries aria-disabled there now, and
not `disabled`, for the reason the Clear button already carries: a dead control
cannot say why. The three bounds are written in ONE place while I was in there;
they were in two, which is two chances to announce a range that is not the one
being clamped to.

AND THE MARKUP STOPS CARRYING A VALUE FOR IT. The comment beside that attribute
argues, correctly, that the FLOOR must not be a literal because it would be a
second copy of a token. The same argument covers the value, and it was applied
to two of the three.

THE SCREEN YOU PINNED GETS THE ROOM. Clicking a screen marked it and left it
exactly the size of the other, so with two browsers open you always watched at
half width - and reading a form the agent is filling in is most of what
watching is. The other screen stays on the stage rather than going away,
because the agent may move to it at any moment and losing sight of that is
worse than a narrow picture. Only when the PERSON has pinned one: the layout
never moves on its own, which is the line this page draws everywhere between
the agent's hand and the reader's eye.

TWO CLOCKS FOR ONE FACT, AND NOW ONE. The address bar had a pump of its own at
two seconds, reading a fleet that a different pump refreshed at three: it could
only ever redraw the same answer between two arrivals, and the one moment it
has to be quick - a screen being clicked - already called it directly. Whoever
changes the fleet tells it. Same shape as the /live/address route, removed for
the same reason.

AND THE COLUMN IS NOT REBUILT WHERE NOBODY CAN SEE IT. The end of every turn
asked the server for the list and rebuilt the DOM inside a panel that is hidden
almost always, on a page that stops every other pump the moment the tab is
hidden for exactly this reason. The boot line already carried the guard, so the
rule was known and applied in one of the two places.

Suite 616 green. Nine known-bad inputs, nine killed.