4 Commits

Include renames

Author	SHA1	Message	Date
Sergey Matyunin	a1b8861eff	fix: preserve plan-only room label scale ... Issue: #167 User-Visible: yes	2026-08-17 13:16:04 +03:00
Sergey Matyunin	7f397a6875	feat: add plan-only space export ... Issue: #167 User-Visible: yes	2026-08-17 12:33:52 +03:00
Sergey Matyunin	053e2a9b68	ci: move workflows to Node 24 actions ... Issue: #145 User-Visible: no	2026-08-16 00:00:36 +03:00
Matysh	328ed7afc0	test: a registry of known breakages that tests must catch ... Five times in this project a green test meant nothing was checked. The continuity smoke stayed green after the entire mechanism it guards was cut out. The golden scene created to protect doorway light was empty — 1,177 warm pixels against 107,119, all of them icons. The shadow smoke passed while no shadow was drawn. Each time the test had been written alongside the code, went green at once, and nobody ever asked whether it could go red. The gate makes that question routine. Each mutant is a few lines of patch that reproduce a known breakage, plus the name of the test that must fail on it. A worktree is patched, the bundle rebuilt, the guard run — and a guard that stays green fails the gate. Six mutants cover the holes documented in #85; the anchors are exact strings from today's source, so the registry cannot silently drift — a unit test that runs with the ordinary suite refuses a stale anchor. The full run rebuilds the bundle per mutant, so it lives in its own workflow, before a stable release and on a weekly schedule, not in Validate. The rules for new tests are written at the top of docs/TESTING.md, and the sixth of them is the cheapest: an assertion that reads back the property the code just set is not written at all. Issue: #85 User-Visible: no	2026-08-14 02:05:53 +03:00