fix: apply WHERE clause check for cross detection in geofence hooks

The WHERE clause was being ignored for cross detection events in
geofence/SETHOOK commands. This happened because testObject() (which
checks WHERE clauses) was only called when an object was spatially
inside the fence. For cross events, both old and new object positions
are outside the fence, so testObject() was never invoked.

This fix adds an explicit WHERE clause check (via fieldMatch) in the
cross detection path before proceeding with event emission. This
ensures that cross events are only triggered for objects that match
the WHERE clause conditions.

Fixes #795

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: majiayu000 <1835304752@qq.com>

Author: 2 people

internal/server/fence.go

@@ -141,6 +141,12 @@ func fenceMatch(
 				}
 			} else {
 				if details.command != "fset" {
+					// For cross detection, the object is outside the fence spatially,
+					// so testObject wasn't called above. We need to check WHERE clause
+					// before proceeding with cross detection.
+					if match, _ := sw.fieldMatch(details.obj); !match {
+						return nil
+					}
 					// Maybe the old object and new object create a line that crosses the fence.
 					// Must detect for that possibility.
 					if !nocross && details.old != nil {