1ac47cd9b7c2cca4edb91e779c1ed03c9ed65722
Some checks failed
CI / go-lint (push) Has been skipped
CI / python-lint (push) Has been skipped
CI / nodejs-lint (push) Has been skipped
CI / test-go-school (push) Successful in 26s
CI / test-go-edu-search (push) Successful in 27s
CI / test-python-klausur (push) Failing after 1m48s
CI / test-python-agent-core (push) Successful in 16s
CI / test-nodejs-website (push) Successful in 18s
Log zeigte: "Invalid control character at: line 28 column 27" Das Pipe-Zeichen | in OCR-Texten (z.B. "| want" statt "I want") bricht den JSON-Parser wenn es als Literal im LLM-Response steht. Fixes: - _sanitize_for_json(): entfernt ASCII Control-Chars 0x00-0x1f (außer Tab/LF/CR die in JSON valid sind) - | → I als erlaubte OCR-Korrektur in _is_spurious_change und Prompt - Reverse-Check in _is_spurious_change (l→I etc.) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Description
No description provided
Languages
TypeScript
60.2%
Python
32.9%
Go
5.5%
C#
0.8%
CSS
0.2%
Other
0.3%