docs: scope the foreign-script and surefire claims to what the code does
hasForeignScript detects by alphabet, so Latin-script leakage such as the observed French "contiennent" is not caught. Say so in the javadoc and admit the gap in the design doc rather than implying coverage. failIfNoTests catches a misplaced or misnamed test class, not a disabled one: an @Disabled class still reports as skipped and the build stays green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F3jSvSTrG4qsniLSr6TpC6
This commit is contained in:
@@ -143,11 +143,17 @@ no function that could do otherwise.
|
||||
| failure | behaviour |
|
||||
| --- | --- |
|
||||
| empty content | retry once at a higher token ceiling, then apologise |
|
||||
| reply contains CJK or other foreign script | discard, retry once |
|
||||
| reply contains a non-Latin script (CJK, Cyrillic, Arabic, …) | discard, retry once |
|
||||
| wiki 403 / timeout / no hit | answer without the article, and say the wiki was not consulted |
|
||||
| MiniMax non-zero `base_resp` | log and apologise; HTTP 200 does not mean success |
|
||||
| tool call absent despite forcing | fall back to answering ungrounded |
|
||||
|
||||
Known gap: the foreign-script check works by alphabet, so it only catches
|
||||
non-Latin scripts. Latin-script leakage — the observed French `contiennent` in
|
||||
an otherwise Portuguese answer — passes straight through, and this design does
|
||||
not close that. Catching it would need dictionary or language-identification
|
||||
work that is out of scope here.
|
||||
|
||||
## Features
|
||||
|
||||
- **Privacy per question.** `/ia` public, `/iap` visible only to the asker.
|
||||
|
||||
Reference in New Issue
Block a user