Skip to content

guard: check a correction against the lexicon after the fact (mirror of #37, with QA fixes) - #38

Merged
Nathaniel-260 merged 2 commits into
mainfrom
mirror/pr37-guard
Nov 16, 2026
Merged

Nathaniel-260 merged 2 commits into
mainfrom
mirror/pr37-guard

Conversation

@Nathaniel-260

Copy link
Copy Markdown
Owner

Mirror of #37 (fork PR; CodeQL does not run on forks) plus QA fixes: aligned words inside split/join units are judged individually, bounded difflib work, no --out creation, guard-specific lexicon messages, documented exit code.

🤖 Generated with Claude Code

mynim and others added 2 commits November 16, 2026 19:53
…mand)

`magiah guard --before FILE --after FILE` lines the two texts up word by
word and judges every change by the corpus frequencies of --out's
lexicon: a common word (>= common_min) that became a rare or unknown one
(<= rare_max) is `suspect` -- the corrector probably broke a good word;
the reverse is `supported`; anything else `neutral`. A split, join,
insertion or deletion is one unit, judged by its least frequent word.
Prints the suspect changes (--guard-all: every change) as TSV and a
count; writes nothing. Nothing else calls it: no scan, finding or score
changes.

* magiah/guard.py: compare (reusable), judge, read_text, run.
* cli: the `guard` command (--before, --after, --guard-all); the
  thresholds from run_config.json / --rare-max / --common-min; the
  lexicon through book_scan.load_lexicon (same refusals).
* README (en/he).
* tests/test_guard.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…k; no --out creation; guard-specific lexicon messages; document exit code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Nathaniel-260
Nathaniel-260 merged commit 838728a into main Nov 16, 2026
13 checks passed
@Nathaniel-260
Nathaniel-260 deleted the mirror/pr37-guard branch November 16, 2026 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants