ref(replay): Trim the v9 AnchoredClock TODOs

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: runningcode

sentry-android-replay/src/main/java/io/sentry/android/replay/capture/BaseCaptureStrategy.kt

@@ -54,11 +54,8 @@ import kotlin.reflect.KProperty
 internal abstract class BaseCaptureStrategy(
   private val options: SentryOptions,
   private val scopes: IScopes?,
-  // TODO [MAJOR]: every value this provider stamps is serialized — segment timestamps and
-  // durations, frame filenames, buffer cutoffs, gesture offsets — and they are all subtracted from
-  // each other, so a clock step corrupts a recording. Replacing it with an io.sentry.time
-  // .AnchoredClock re-bases those timestamps and is therefore v9-only. See JAVA-575.
-  private val dateProvider: ICurrentDateProvider,
+  // TODO [v9]: We should consider replacing this with AnchoredClock in V9.
+  dateProvider: ICurrentDateProvider,
   private val ticker: MonotonicTicker,
   protected val replayExecutor: ScheduledExecutorService,
   protected val persistingExecutor: ScheduledExecutorService,

sentry-android-replay/src/main/java/io/sentry/android/replay/gestures/ReplayGestureConverter.kt

@@ -13,8 +13,7 @@ import io.sentry.transport.ICurrentDateProvider
 import java.util.concurrent.TimeUnit.MILLISECONDS
 
 internal class ReplayGestureConverter(
-  // TODO [MAJOR]: the timestamps and timeOffsets stamped from this provider are serialized, so
-  // moving them onto an io.sentry.time.AnchoredClock is v9-only. See JAVA-575.
+  // TODO [v9]: Replace this with AnchoredClock in V9
   private val dateProvider: ICurrentDateProvider,
   private val ticker: MonotonicTicker,
 ) {