test(maestro): keep optional-scroll continuation assertion visible
Summary
Keep the optional-scroll conformance flow's continuation assertion visible after scrolling. The fixed Home tab replaces reliance on an off-screen page heading. Both optional operations, their timeouts and the initial title assertion remain unchanged.
One test fixture, +1/−1; part of #3377. No runtime changes.
Validation
Head 94bd20831bb796e0b3fe9dda7df573a036c98569; base e401de82d5a23bedbd88de68156862f8cc49ddca.
On unchanged base, upstream Maestro and agent-device both fail the original final heading assertion. The committed head passes the same Android differential scenario on both engines through the T3-bound source daemon. Cleanup passed. Updated iOS differential verification also passed both engines, with warnings on both optional steps and successful final Home. Source-daemon routing and cleanup were verified; the cached fixture build SHA is unrecorded.
Independent source review found no regressions. Hosted checks: 7 success, 5 skipped, 1 neutral.
Pinned pnpm 11.17.0 frozen install/build and the single post-review affected run exited 0. Receipt run-xGUbuq: 42 passed, 25 skipped, exactCommit=true, checkoutChanged=false; provider integration passed 288 tests. Default origin/main selection was preserved; actual PR diff was recorded separately.
Earlier run-bl6mNY remains a failed receipt due to an Android-alert timeout; its cause is unproven. This new pass neither erases nor explains it. Canonical Maestro performance and npm prerequisites remain separate C3 blockers. The fixture correction has independent source review, exact-head admission and Android/iOS evidence. It does not clear the separate plugin-extraction blockers.