test: wait for live status to settle after reconnect
Summary
The 5.0.1 candidate dry-run (run 39236003027) failed live-ssr-sharing-update-and-reconnect in the new development lane. SER reported Connecting while native reported Open.
Live.status samples its resource every 250 ms. Native reads resource.connected straight from the template. So after a reconnect, SER's status can trail the first new value by up to one sample. The scenario already waits for Open before its initial reads. It now does the same before the final read after the reconnect. Both targets must still reach the same status.
Verification
Live queriesscenario with--repeat-each 5: passes in development and production.
š¤ Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3.svg)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark.svg)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the live reconnect test so it waits for both targets to report Open status after reconnect before asserting the final state. Live.status samples its resource every 250 ms, so after reconnecting, the status can trail the first new value by up to one sample. The test now waits for Open on both left and right clients before the final reads, aligning with the initial wait and preventing flaky failures when SER still reports Connecting.