Frontend note: the fix is not done until the next reader can see why

A Frontend Lab note about leaving compact evidence after a UI fix lands.

A frontend fix often looks complete when the layout stops jumping. But the next reader still needs to know which constraint actually mattered. I try to leave three things: the failing viewport, the rule that stabilized it, and the tradeoff I accepted. That is enough for someone else to avoid reopening the same bug with a different label. The note does not have to be long. In fact, long explanations can hide the useful part. A short trail that names the constraint is usually better than a polished paragraph that says the component was improved. The fix is visual, but the memory is structural.