fix(ci): pass --maestro and match the fixture app's real UI in layer-3 flows

Run 4 (29500262301) reached the differential itself — build, install, simctl
check and the pinned Maestro 2.5.1 verification all passed — and surfaced two
real bugs, both mine:

1. The runner invoked `agent-device test <flow>` without --maestro, so every
   scenario failed with "test does not support this file type". The repo's own
   scripts/run-test-app-maestro-suite.mjs passes it; the flag is what routes a
   .yaml through the Maestro compat engine.

2. settle-after-tap and percent-swipe assumed home-open-form is on screen at
   launch. It is not: real Maestro reported "Element not found: home-open-form",
   and the app's own helper flow scrolls it into view first. settle-after-tap now
   scrolls before tapping, mirroring that helper; percent-swipe no longer
   navigates at all and swipes the scrollable home screen, so it tests the
   conversion and nothing else.

The remaining two flows already reported maestro=pass, so only the agent-device
invocation was wrong for those. Note the settle invariant correctly reported
"no-data: no completed tapOn steps" and FAILED rather than passing — a detector
that cannot run is a failure, as intended.

Author: thymikee

scripts/maestro-conformance/differential/flows/percent-swipe.yaml

@@ -1,12 +1,11 @@
-# Layer-3 device flow (bug class 1, runtime half). Percentage endpoints must
-# resolve to the same pixels on both engines (integer division, not rounding).
+# Layer-3 device flow. Percentage swipe endpoints must drive the same gesture on
+# both engines. Deliberately stays on the scrollable home screen: no navigation,
+# no off-screen controls, so the scenario tests the swipe and nothing else.
 appId: com.callstack.agentdevicelab
 ---
 - launchApp:
     clearState: true
-- tapOn:
-    id: home-open-form
-- assertVisible: Checkout form
+- assertVisible: Agent Device Tester
 - swipe:
     start: 50%, 75%
     end: 50%, 35%

scripts/maestro-conformance/differential/flows/settle-after-tap.yaml

@@ -1,10 +1,16 @@
-# Layer-3 device flow (bug class 4). Real tap on a real element of the lab app,
+# Layer-3 device flow (bug class 4). A real tap on a real control of the lab app,
 # so the post-tap settle loop actually runs and the timing invariant is meaningful.
+# home-open-form sits below the fold, so scroll it into view first — the app's own
+# helper flow (examples/test-app/maestro/helpers/open-checkout-form.yaml) does
+# exactly this; tapping it directly fails with "element not found".
 appId: com.callstack.agentdevicelab
 ---
 - launchApp:
     clearState: true
 - assertVisible: Agent Device Tester
+- scrollUntilVisible:
+    element:
+      id: home-open-form
 - tapOn:
     id: home-open-form
 - assertVisible: Checkout form

scripts/maestro-conformance/differential/run.ts

@@ -119,9 +119,12 @@ function runScenario(scenario: DifferentialScenario, options: RunnerOptions): Sc
   const platformArgs = options.platform ? ['--platform', options.platform] : [];
 
   const maestro = runEngine('maestro', options.maestroBin, ['test', flowPath, ...platformArgs]);
+  // `--maestro` is required: without it `test` rejects a .yaml flow outright
+  // ("test does not support this file type"). Matches scripts/run-test-app-maestro-suite.mjs.
   const agentDevice = runEngine('agent-device', `node ${options.agentDeviceCli}`, [
     'test',
     flowPath,
+    '--maestro',
     ...platformArgs,
   ]);