#3560 Flaky: LitestreamReplicator.acquire 'concurrent acquires in one process share one sidecar and one hold' fails 'no hold leaked' under full-suite load

src/infrastructure/datastore_v3/litestream/litestream_replicator_test.ts:578 failed in a verify-build run (run b0ac5c9c-c5bc-492a-8ca8-7c05ff40db88, commit 0801303f5, a change that only touched src/domain/vaults/mock_vault_provider.ts). The final assertion at line 606 failed: after both a.release() and b.release(), a fresh tryLock(true) on world.paths.useLock returned false (AssertionError: no hold leaked, actual false, expected true). The same file passed 8 of 8 runs on its own, so this looks like a timing dependence that only shows under deno test --parallel load: the use-lock hold is probably not fully dropped by the time b.release() resolves, or another acquirer still holds it. Found while verifying swamp-club#3559; unrelated to that work, so filed separately. Fix: make release() resolve only once the flock is actually dropped, or have the test poll with waitFor instead of asserting immediately, per the AGENTS.md timing rules.