Arnas Donauskas ca3aa29c3a fix(automations): persist default match_type for Keyword Match triggers ... Creating a keyword_match automation with Match type left on the default "Contains" failed activation with `match type must be "exact" or "contains"` (path trigger.match_type). The dropdown showed "Contains" via a display-only fallback, but the value was never written to the config, so the saved payload omitted match_type entirely. Both engines already treat a missing match_type as "contains" (automations/engine.ts, flows/engine.ts), so the activation validator was stricter than runtime. Two coordinated fixes: - validate.ts: accept a missing match_type (defaults to "contains"); only an explicit, unrecognised value is rejected. Aligns the validator with the engines and any non-UI client. - automation-builder.tsx: seed match_type: "contains" on mount of KeywordMatchConfig so the displayed default is actually persisted, keeping the saved record explicit and self-describing. Adds a regression test that a keyword_match config with no match_type passes activation validation. Fixes #271 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-22 10:20:38 +03:00
..
automation-builder.tsx	fix(automations): persist default match_type for Keyword Match triggers	2026-06-22 10:20:38 +03:00