fix: alert filter validation for property conditions

When creating filters on custom properties, the column should be
"properties" with the property name in the "key" field. Previously the
filter was incorrectly setting the property name as the column directly.

Also added backward compatibility for existing filters that used the
old format.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: colegottdank

web/filterAST/components/FilterConditionNode.tsx

@@ -199,12 +199,18 @@ export const FilterConditionNode: React.FC<FilterConditionNodeProps> = ({
     })();
 
     // Create updated condition with new field and default operator
+    // For property and score subtypes, the column should be "properties" or "scores"
+    // and the actual field name goes in the "key" property
+    const isPropertyOrScore = filterDef.subType === "property" || filterDef.subType === "score";
     const updated: ConditionExpression = {
       ...condition,
       field: {
-        column: fieldId as any, // Use 'any' to bypass type checking temporarily
+        column: isPropertyOrScore
+          ? (filterDef.subType === "property" ? "properties" : "scores") as any
+          : fieldId as any,
         subtype: filterDef.subType,
         table: filterDef.table,
+        ...(isPropertyOrScore && { key: fieldId, valueMode: "value" as const }),
       },
       operator: defaultOperator,
       value: defaultValue, // Reset value since field changed
@@ -240,7 +246,13 @@ export const FilterConditionNode: React.FC<FilterConditionNodeProps> = ({
   };
 
   // Find the filter definition for this field
-  const filterDef = filterDefs.find((def) => def.id === condition.field.column);
+  // For property/score subtypes, look up by the key field, otherwise by column
+  // Handle backward compatibility: old filters may have property name in column instead of key
+  const isPropertyOrScoreSubtype = condition.field.subtype === "property" || condition.field.subtype === "score";
+  const filterDefId = isPropertyOrScoreSubtype
+    ? (condition.field.key || condition.field.column)  // fallback to column for backward compatibility
+    : condition.field.column;
+  const filterDef = filterDefs.find((def) => def.id === filterDefId);
 
   // Get available operators
   const operators = filterDef?.operators || [];
@@ -410,7 +422,7 @@ export const FilterConditionNode: React.FC<FilterConditionNodeProps> = ({
     >
       <SearchableSelect
         options={fieldOptions}
-        value={condition.field.column}
+        value={filterDefId}
         onValueChange={handleFieldChange}
         placeholder="Select field"
         searchPlaceholder="Search field..."