In brief
A style repair is durable only when the next build preserves it. The recent Units progress repair changed the generated markup, its external stylesheet and the generator checks together. The subsequent release removed the remaining embedded style blocks from two monument studies and verified their rendered appearance.
The generator is part of the styling system
A generated progress display can look correct while carrying presentation rules in its HTML. Editing the generated page alone would leave the next build free to restore them. The Units repair instead uses named classes for its progress rods, with the presentation held in the shared external stylesheet. Generator assertions check the same contract.
This joins three responsibilities that are easy to separate accidentally: the markup describes the state, the stylesheet presents it, and the generator reproduces both consistently. The Units library and Analysis report remain views of the underlying registers, rather than independent places to type progress values.
Preserving the picture is a separate check
The remaining embedded styles on Angkor Wat and Stonehenge were extracted into page-specific external stylesheets at the same cascade position. The rules were moved without redesigning the approved graphics or changing historical claims. Desktop and narrow-screen comparisons checked that the resulting pages retained their appearance.
One early narrow-screen comparison differed while fonts were settling. A later capture taken after the fonts were ready matched. That matters because a screenshot comparison can report a rendering-timing difference as if it were a design regression. A source scan answers whether presentation has moved out of the HTML; a settled render answers whether the reader still sees the intended page.
Check the whole output after a shared repair
The full external-CSS scan passed across all 261 production HTML pages in the remediation release. The shared scripts were also checked for presentation writes. The release process now repeats the full-tree gate, so a later generator change cannot quietly reintroduce the same class of defect elsewhere.
This is a bounded result. Component consistency, accessibility, media performance and public status still have their own acceptance work. Passing the stylesheet gate does not close those lanes, and improving a display does not count as a new historical enrichment.
The Case Studies keep the evidence and interpretation; the Build Log keeps the implementation lesson. Fix the source of generated output, then verify both its structure and its appearance before calling the repair durable.