0.13.2 — no engine name in the browser

Since 0.9.0 an instance with the credit switched off does not ship the engine name in its JavaScript bundle: the decision is made at build time and the dead branch disappears. That closed one place. Reviewing the 0.13.1 pull requests showed there were others.

In the bundles of uncredited instances the engine name sat in the names of two animation classes and their keyframes, in four browser event names, and from 0.13.0 it was about to arrive in the HTTP language header. None of these places are visible on the page. All of them are visible to anyone who opens the file — which is exactly the person the credit is switched off for.

classes and animations   tetno, tetno-fala, kursor-konsoli, kursor-miganie
events                   site:account, site:star, site:stars-collected, site:stars-total
language header          x-site-lang

There is a new guard, `check-engine-name.mjs`: after the build it goes through everything that is sent to the browser and stops if an uncredited instance carries the engine name. A credited instance passes straight away. An instance that used the old classes in its own content has to rename them — the only change required on its side.