4 Commits

Include renames

Author	SHA1	Message	Date
Codex	273b0d5ecb	test: the backend mutant follows the registry convention (#329 r2-H1) ... The reviewer is right twice over. My previous commit fixed the red CI by relaxing the contract — a guard could name a `.py` file — when the registry already had a convention for exactly this case: every backend mutant runs `node scripts/backend-test-guard.mjs <pattern> <file>`, which owns the python executable choice and the `-k` selection. Bending a rule to fit my one-off is the worse of the two possible fixes, so the contract goes back to demanding a `.mjs` guard, and junction-limit-backend-raw-baseline now uses the helper and targets the one test that proves the migration (test_legacy_baseline_is_judged_after_the_same_migration). Re-verified: registry --check clean, the mutant still catches its regression 1/1, npm test 1390 passed / 0 failed. Issue: #329 User-Visible: no	2026-08-28 00:41:30 +03:00
Codex	26c6e87079	test: a mutant guard may be pytest, not only node (#329) ... The registry contract demanded that every guard name a `.mjs` file, which was true until this task added the first backend mutant — junction-limit-backend-raw-baseline is guarded by pytest, and the mutation-gate job already installs it. My mistake: I ran `--check` and the single mutant after adding it, but not the unit suite that owns the registry contract, so CI caught what I should have. The contract keeps its point: a guard must name a file that exists. Issue: #329 User-Visible: no	2026-08-28 00:28:12 +03:00
Matysh	3aba493b25	fix: compile test-build inside the mutant worktree ... Issue: #235 User-Visible: no	2026-08-22 11:24:37 +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