yu 624d13f2ef fix: StrUtil_Replace enum mapping - search select value was treated as literal text ... Catalog contract: search is a select ("0"=content / "1"=digits / "2"=phone / "3"=email / "4"=ID card / "5"=custom regex) with the target in Config. Old implementation used first(args, ["search","Config"]) so the enum value "0" was split on as literal text, making content-replace never work (same family as W26-W33 enum mapping bugs). Now implements all six modes with preset patterns, regex mode guarded by try/catch, and falls back to legacy literal behavior when Config is empty.		2026-11-05 13:22:43 +08:00
..
rpa-core	fix: StrUtil_Replace enum mapping - search select value was treated as literal text	2026-11-05 13:22:43 +08:00