mirror of
https://github.com/penpot/penpot.git
synced 2026-11-21 01:22:01 +00:00
With `debug`, the browser replay logs each target and the shapes every program ends with whether the WASM engine is on or off, so a WASM failure can be compared with the same program on the plain engine. Harness only; the benchmark is not run. Also in this commit: - Apply the generated typography only where the file holds it. A text style edit picks the generated typography for one of its values, but only worlds with text styles add that typography to the file. In the others the model applied the edit's styles while the frontend applied a missing typography, which sets no style, so the two diverged. The edit names the typography only when the file holds it. - Replay programs in the browser as the frontend tests do. The browser replay mocks the backend and the timers as the frontend generated tests do, turns the WASM engine off for the plain engine even when the page's configuration turns it on, and in debug logs the content a text edit commits and each text's characters and font weights. - Name the boards a deleted component's main was held by. The canonical design data names shapes and components by their place in the tree, so the model and the frontend compare although each allocates its own ids. A deleted component keeps the ids of the board that held its main, as a variant's component keeps its container's once the variant is undone; with that board gone the ids stayed raw and differed between the two runs. They are named after the component when no live shape is. - Report where the model and the frontend first differ. A backend mismatch in the frontend replay printed the whole diff of the two canonical designs, which lists float noise the comparison accepts next to the difference it rejects. `oracle/inequivalence` walks the two designs as `equivalent?` compares them and returns the path of the first rejected value with both sides; the mismatch message leads with it. - Keep text sizes and take inline programs in the browser replay. With the WASM engine on, the replay keeps each text's stored size in place of the engine's text resizes: the model keeps stored sizes, and the generated texts are too narrow to measure, so a new copy's measured text differed from its main's unmeasured one. The page also takes the programs inline in an `edn` query parameter, which a shrink loop drives. AI-assisted-by: claude-opus-5-5