mirror of
https://github.com/saphid/frame-control.git
synced 2026-10-22 04:09:47 +02:00
saphidandClaude Opus 5.5
7fe7e504da
- A Frame error during a test (an ssh failure with empty stderr raises its stdout, which can be the game's log) becomes the fixed "couldn't read the game's log from the Frame" message, with no original text and no chained cause. run_test wraps every step; the /api/meta test job also maps any other exception to a fixed text, and the CLI and Install and test go through run_test. Close failures no longer echo their error text. - Log scans are linear: signatures look at the first 4 KB of each line and every repetition followed by more required text is bounded; excerpts split the redacted line once and fullmatch only words of 64 characters or less; the generic OC/FRL token pattern matches each run once (no lookahead) and keeps it unless it has a digit. Timing tests: 100 KB adversarial lines through classify, redact and every excerpt each finish well under 200 ms (the old library and token patterns took 19 s and 9 s). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>