Backstage

A first extraction stopped with browser engine not available instead of printing a design system, and the fix the error named did not work either.

Dembrandt drives a real browser, and it has to be the exact version Dembrandt expects. The browser install we documented fetched whatever was newest instead. The two stopped matching on 9 August, and the instruction had been correct for months before that.

You installed Dembrandt, ran it on a site, and got an error instead of a design system. If you had used it before on the same machine, it kept working.

Your CI job stopped recording snapshots. If it wrapped the command in || true, it went green the whole time and told you nothing.

Your history in the App has a gap for those dates, and the drift score on those domains is older than it looks. Open a domain and it rescores.

Upgrading is enough. A run that finds no browser now installs the right one and carries on.

Staying on an older version: run dembrandt install-browser once.

Install and run. If the browser is missing, Dembrandt downloads it once and finishes the extraction you asked for. There is no separate install step to remember or to get wrong.

In CI, drop the browser install line. dembrandt install-browser still works if you would rather pay the download in its own step, and it can no longer fetch a version that does not match.

Nothing about extraction changed, so committed baselines and drift gates read the same after upgrading.