test(ui): automation runner gains click at <x> <y> — raw synthetic canvas click

The vitals round's connected verify needed to click ONE specific
Character-tab option row, but every toggle row is a template instance
sharing the same dat element ids (0x10000218/0x10000219), so
`click element` (first-match by dat id) cannot address a row. The drive
script now reads the row's rect from its own `dump` line and clicks its
center — same synthetic UiRoot press/release route as ClickElement, never
the OS cursor (the same no-real-input constraint the morning gate's
hover/mousemove verbs follow).

Used live: the Side-By-Side Vitals checkbox + Apply choreography that
verified db8fa328's swap both directions over a real ACE session.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

src/AcDream.App/UI/Testing/RetailUiAutomationProbe.cs

@@ -131,6 +131,22 @@ public sealed class RetailUiAutomationProbe
         return true;
     }
 
+    /// <summary>
+    /// Raw synthetic click at canvas coordinates (vitals retail-modes round,
+    /// 2026-08-17): the Options panel's Character-tab rows are template
+    /// instances sharing ONE dat element id per control
+    /// (<c>0x10000218</c>/<c>0x10000219</c> for every toggle row), so
+    /// element-id addressing cannot reach a SPECIFIC row's checkbox — a
+    /// drive script instead reads the row's rect from <see cref="DumpText"/>
+    /// and clicks its center. Same synthetic <see cref="UiRoot"/> route as
+    /// <see cref="ClickElement"/> — never the OS cursor.
+    /// </summary>
+    public bool ClickAtPoint(int x, int y)
+    {
+        ClickAt(x, y);
+        return true;
+    }
+
     /// <summary>
     /// 2026-08-17 morning gate: synthetic pointer HOVER (no click) at an
     /// element's center, for rollover/tooltip verification. Deliberately