test: avoid inspecting an absent demo destination

Check that the original thread row has disappeared before querying Back readiness, preserving both destination conditions and the existing retry budget.

Coven-Harness: Codex / gpt-6-astra

Author: BunsDev

apps/ios/ModexCompanion/UITests/DemoWorkspaceTests.swift

@@ -341,7 +341,7 @@ final class DemoWorkspaceTests: XCTestCase {
     private func openDemoThread(_ app: XCUIApplication, timeout: TimeInterval = 30,
                                 tap: ((XCUIElement) -> Void)? = nil) -> Bool {
         let thread = app.buttons["thread-demo-launch"]
-        let opened = { app.buttons["Back to threads"].isReadyToTap && !thread.exists }
+        let opened = { !thread.exists && app.buttons["Back to threads"].isReadyToTap }
         var initiated = false
         return completeDemoAction(
             timeout: timeout,

docs/status.md

@@ -681,6 +681,9 @@ seven site tests, with real OpenKnowledge enabled and no skips.
   opening and Back actions. In job `114763678754`, the initial row tap left the dashboard
   visible; native evidence does not establish why. This is a test correction, with hosted
   native verification required before merge; app navigation is unchanged.
+  The destination check first requires the original row to disappear: job `114806660312`
+  repeatedly inspected the absent Back button and exhausted the retry budget without a
+  real thread tap. Both destination conditions and the two-attempt, 30-second budget remain.
 - **Native and renderer sizing in desktop tests.** The layout helper can make one native
   size transition when the renderer stays at different dimensions despite correct native
   bounds. It observes the intermediate dimensions before restoring the target and still