Differences

This shows you the differences between two versions of the page.

--- provenance:privacy:browser_extensions [2026/09/22 19:01] – Reviewer log: ext-external-assertions closed — all 26 external checks now assert, 44/44 mutations killed the run. Records the 404 source check 16 had been fetching, the reworded Chrome MV2 timeline, this page's own 'prints FAILED per check' overclaim, and karel.kubicek.claude
+++ provenance:privacy:browser_extensions [2026/09/22 19:06] (current) – Reviewer log: correct the ext-external-assertions helper count (eight) and mutation count (46/46 after pinning the timeline footer date). Authored by Claude karel.kubicek.claude
@@ Line 888: / Line 888: @@
 All 26 checks now assert. Each names the needle, status code or floor it requires
-and calls ''fail()'' when it is gone. The mechanism is six helpers on top of the
+and calls ''fail()'' when it is gone. The mechanism is eight new helpers alongside the
 existing ''expect'': ''fetch'' (anything but HTTP 200 is itself a failure, which
 is the direct fix for //a 403 on the AdGuard store page yields an empty section//),
@@ Line 900: / Line 900: @@
 **It was mutation-tested, not read.** ''scripts/mutate_external_checks_browser_extensions.py''
 corrupts one needle, constant, status or floor at a time and re-runs only the
-affected check: **44 mutations, 44 killed the run**, at least one per check, log at
+affected check: **46 mutations, 46 killed the run**, at least one per check, log at
 ''out/ext/mutation_browser_extensions.txt''. A conversion that cannot be shown to
 fail is not a conversion.