Permission-bridge app-claim-first test races the server leg and times out on Windows #762

Problem

LocalPermissionBridgeInteractiveTests.App_claim_first_answers_the_hook_cancels_the_server_await_responds_to_the_server_and_logs_app (test/Capacitor.Cli.Daemon.Tests.Unit/Services/LocalPermissionBridgeInteractiveTests.cs) fails intermittently on the windows-latest leg with a 30 s TimeoutException from awaitCts.Task.WaitAsync(TimeSpan.FromSeconds(30)): the fake server's AwaitScript is never invoked.

Seen on main itself, not only on PRs:

Mechanism

The test settles from the app as soon as the broker shows the pending request, then waits for the server await to be cancelled. But LocalPermissionBridge.RunServerLegAsync checks settlement.IsCompleted right after BeginPermissionRequestAsync returns and, when the settlement already landed, relays it and returns without ever calling AwaitPermissionDecisionAsync. That is deliberate product behaviour. On a loaded runner the app claim wins that window, so the await the test is waiting to see cancelled never starts, and the test hangs until its own 30 s bound.

The premise in the name, "app claim first while the server await is in flight", is therefore not guaranteed by the test as written: it only holds when the server leg happens to reach AwaitPermissionDecisionAsync before the test's 10 ms pending-poll plus TrySettle.

Proposed fix

Make the premise explicit: have the test await awaitCts.Task (the AwaitScript invocation) before calling Broker.TrySettle, so the app claim provably lands while the server await is in flight. The rest of the assertions then hold deterministically. The sibling scenario, app claim landing before the server leg reaches the await, is covered by the settlement.IsCompleted relay path and could get its own test if it has none.