test(robots-check): pin the tie-break clause and the browser-UA fallback

The tie-break test listed Disallow first - the one ordering where
deleting the clause changes nothing - and gate()'s read-the-policy-as-a-
browser recovery (the Barclays-class case 09-web-research.md documents
as covered) had no test. Both gaps are guard code whose breakage is
silent by construction. Mutation-verified: the tie-break deletion and
the UA-loop reduction each now fail exactly the new tests. Review
findings F21 and F30 (2026-08-19).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-08-19 19:57:46 +02:00
co-authored by Claude Opus 5
parent 4ed5fee221
commit c20458d768
2 changed files with 57 additions and 0 deletions
+7
View File
@@ -15,6 +15,13 @@ per-file diff commands.
### Added
- **Discriminating tests for `robots_check`'s tie-break and browser-UA fallback** - the
existing tie test put Disallow first, the one ordering that cannot detect deletion of
the tie-break clause; and the browser-readback recovery that `09-web-research.md`
claims is covered had no test at all. Three new tests in `tests/test_robots_check.py`
pin the Allow-first tie, the 403-to-honest/200-to-browser recovery, and that a
browser-fetched policy is still obeyed strictly. Each was mutation-verified: deleting
the tie-break clause or the UA fallback now fails the suite.
- **LaTeX special-character guidance for CVs** (`framework_version` 1.4.1 -> 1.4.2 in
`05-cv-templates.md`, 1.0.1 -> 1.0.2 in `06-cover-letter-templates.md`) - `05` gains a
"LaTeX Special Characters" section and `06`'s existing one is completed beyond `\_`/`\&`.