Knock fallback workflows: allow time for delivery state to change

For the Knock entry, a fallback decision can run before the information it needs exists. The step-condition guide explains that delivery is asynchronous while conditions on the next step are evaluated immediately.

If a later channel depends on whether an earlier notification was delivered or read, include an appropriate delay before evaluating that status. Otherwise an apparently sensible condition can trigger the fallback too early.

Test with both prompt and delayed delivery. Record when the condition is evaluated, not just the final status visible later.