docs: correct stale references to workflowInfo().startTime in comments

Signed-off-by: Joana Maia <jmaia@contractor.linuxfoundation.org>

Author: joanagmaia

services/apps/security_best_practices_worker/src/activities/index.ts

@@ -190,7 +190,7 @@ export async function saveOSPSBaselineInsightsToRedis(
 function classifyTokenError(output: string, source: string): void {
   // Wall-clock timestamp of the failure. Passed via ApplicationFailure.details so the
   // workflow can persist an accurate rateLimitedAt — workflow code can't call Date.now()
-  // itself (Temporal determinism rule; workflowInfo().startTime skews on long batches).
+  // directly (Temporal determinism rule).
   const failedAtMs = Date.now()
 
   if (output.includes('401 Unauthorized') || output.includes('401 Bad credentials')) {

services/apps/security_best_practices_worker/src/workflows/triggerSecurityInsightsCheckForRepos.ts

@@ -117,8 +117,9 @@ export async function triggerSecurityInsightsCheckForRepos(
         const appFailure = unwrapApplicationFailure(error)
         if (appFailure?.type === 'Token403Error') {
           tokenInfo.isRateLimited = true
-          // Activity captures the wall-clock time of the 403 in details[0]; fall back to the
-          // batch startTime when details are missing so we still record something.
+          // Activity captures the wall-clock time of the 403 in details[0]; fall back to
+          // the iteration's currentTimeMs (from the getCurrentTimeMs activity) so we still
+          // record something when details are missing.
           tokenInfo.rateLimitedAt =
             extractFailureTimestamp(appFailure) ?? new Date(currentTimeMs).toISOString()
           sawRateLimit = true