Flaky TestAnyCommandCombinationFlow: fixed 1s sleep before checking COMPLETED #662

Observed

TestAnyCommandCombinationFlowCadence failed twice under heavy local load: once in a full Cadence run and once when rerun in isolation. It passes in CI on clean runners (#661).

• Assertion: server/integ/any_command_combination_test.go:161 expects FLOW_STATUS_COMPLETED, but the Flow is still FLOW_STATUS_RUNNING.
• Cause, partly verified: the test calls PublishToChannel, then time.Sleep(1 * time.Second), then describes the Flow once. Under load, Step S2 is still processing after 1 second.
• This was observed on branch codex/rt-delete (multi-tenancy removal), which does not touch this code path. The local machine's load average was 12–20.

Where to look

server/integ/any_command_combination_test.go, around the PublishToChannel → sleep → describe sequence near line 161.

Acceptance criteria

• Replace the fixed sleep with convergence, for example require.Eventually on the Flow status, or WaitForFlow with a bounded timeout. Keep the existing assertions about the final state and history. Do not relax them.
• The repo rule says no time.Sleep in tests except inside the behavior under test.
• The test passes 10 times in a row on both Temporal and Cadence while the machine is loaded, for example with a parallel CPU burner or GOMAXPROCS=2.