OLmatter 4810ce289b fix(gui): /captcha_direct path still used old [direct] print without timing ...

The [direct] 识别成功 log line (captcha_server.py line 492) was the one users
actually saw - it had no timing. My earlier [captcha] print landed on the
[CAPTURE] path (auto-capture), a DIFFERENT code path. Replace the [direct]
success/fail logs with the same [captcha] summary including end-to-end + yolo
+ ocr timing. Now both paths print timing consistently.

2026-06-23 04:41:37 +08:00

..

monitor

Fix backend browser capture compatibility

2026-05-26 22:31:25 +08:00

release

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

tools

fix(gui): /captcha_direct path still used old [direct] print without timing

2026-06-23 04:41:37 +08:00

userscripts

revert(userscript): 回退到 v8.19 (e07ec9e)

2026-06-15 23:43:30 +08:00

bootstrap_windows.ps1

fix(install): PowerShell ate -i as param name -> pass pip args as ;-joined string

2026-06-23 03:38:36 +08:00

one_click_start.ps1

feat(install): auto-select PyPI mirror with multi-source fallback

2026-06-23 03:50:05 +08:00

setup_backend_macos.sh

feat(macos): add backend setup and launch support

2026-06-20 14:27:31 +08:00

setup_backend.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00

setup_backend.py

fix(install): mirror never reached pip - argparse ate -i as a flag

2026-06-23 03:21:50 +08:00

start_backend.ps1

fix(ps1): add UTF-8 BOM to all .ps1 to fix PS 5.1 ParserError on CN Windows

2026-06-23 03:07:52 +08:00