condition-based-waiting

Replace arbitrary `setTimeout` calls with condition-based waiting that polls for actual state changes. This eliminates race conditions by waiting for events or conditions to occur rather than guessing how long they'll take, ensuring tests pass reliably in CI and parallel environments.

Condition polling waits for a specific condition to become true before proceeding, adapting to actual execution speed. `setTimeout` waits a fixed duration regardless of whether the condition is met, creating race conditions and flaky failures under load or in CI.

Use a generic `waitFor` polling function with a condition predicate and configurable timeout. The function repeatedly checks your condition until it returns true or the timeout expires, with specialized helpers like `waitForEvent` for common async patterns.

Yes. Condition polling is designed for async operations and parallel CI environments. By waiting for actual state changes instead of fixed delays, tests execute faster and remain reliable regardless of execution order or system load.

The `waitFor` function throws a timeout error after the configurable timeout expires, providing clear failure messaging. This replaces silent test hangs or inconsistent passes, making debugging race condition failures faster.