#3791 flaky: LitestreamReplicator 'a failed launch releases its lock probe, so the next acquire starts a sidecar' fails by timing in verify-build

Problem

src/infrastructure/datastore_v3/litestream/litestream_replicator_test.ts, test 'LitestreamReplicator: a failed launch releases its lock probe, so the next acquire starts a sidecar', failed in a verify-build run with 'Values are not equal: no lock left held' (actual false, expected true) on a change that touches no datastore v3 file (swamp-club#3732, commit 30a85fc7752f5b6b99ba416c41e23319dfeeedba, run 4ad1db4a-0901-4609-8e18-edcd97febc6a). Three local runs of the file pass (29 tests each). The verification host runs the full suite in parallel, so the lock probe release looks timing-sensitive under load.

Expected

The test waits for the probe's release with waitFor on the observable state rather than asserting it right after the failed launch, or the replicator releases the probe before the launch failure surfaces to the caller, whichever the implementation intends. Include it in the scheduled flaky-test job's triage.