[feiyang3cat]

What changed?

Use the workflow’s virtual clock when rescheduling activities through reset/unpause operations and determining whether pending activities are waiting for retry backoff.

Convert workflow task scheduled/started timestamps to real time before comparing them with physical timeout task timestamps for best-effort deletion.

Why?

After time skipping, the workflow’s virtual clock differs from the shard’s real clock. Mixing these clocks can:

• Reschedule activities in the past, bypassing jitter delays and potentially causing premature schedule-to-start timeouts.
• Report activities as waiting for retry backoff even though their retry time has passed.
• Incorrectly include long workflow task timeout tasks in best-effort deletion, bypassing the two-minute limit.

These issues also apply after time skipping is disabled because the accumulated offset remains.

How did you test it?

• built
• run locally and tested manually
• covered by existing tests
• added new unit test(s)
• added new functional test(s)