Greptile Summary

This PR fixes a longstanding stale-timestamp bug in appendCronStyleCurrentTimeLine where the early-return guard base.includes("Current time:") caused heartbeat and cron prompts to carry the timestamp from the very first run indefinitely. The fix swaps that guard for a regex substitution (/^Current time:.*$/m) that always replaces the existing line with a fresh one, while still appending when no line is present.

Key observations:

• The core logic change is correct and minimal — one guard removed, one regex branch added.
• The regex is constructed fresh on every call (no lastIndex state leakage), and .replace() without the g flag intentionally updates only the first match, which is the right behavior given the no-duplicate invariant enforced by the same function.
• post-compaction-context.ts already worked around this bug by calling resolveCronStyleNow directly; it is not broken by this change. The PR description slightly overstates the scope of the fix for that file.
• session-reset-prompt.ts calls the helper with a constant string that never contains Current time:, so it was not affected by the original bug, but it will benefit if callers ever pass a previously-enriched prompt string.
• Tests are thorough and directly exercise the regression scenario.

Confidence Score: 5/5

• This PR is safe to merge — the change is small, well-tested, and strictly improves correctness with no regressions.
• The fix is minimal and targeted: one condition removed, one regex branch added. The regex is stateless (fresh object per call), replacement semantics are correct, and six new tests directly cover the regression scenario plus all relevant edge cases. Callers in heartbeat-runner.ts and the web variant pass freshly resolved startedAt/nowMs values, so the refreshed timestamp will always be current. No existing tests were modified and no unrelated files were touched.
• No files require special attention.

_{Last reviewed commit: 2f0bf3b}

Closing this as not reproducible on current main after Codex review.

Closing as cannot reproduce. On current main, the stale-between-runs path described in the PR does not exist: heartbeat prompts are rebuilt from raw config/system-event text for each run, and the previously injected timestamp is not fed back into appendCronStyleCurrentTimeLine. The proposed regex replacement would also rewrite arbitrary user-authored cron reminder lines that start with "Current time:".

What I checked:

• Helper only skips when input already contains a time line: appendCronStyleCurrentTimeLine still returns early when the incoming text already contains "Current time:"; the PR targets this branch. (src/agents/current-time.ts:33, 40be5ad58187)
• Heartbeat prompt is rebuilt from raw queued event text each run: resolveHeartbeatPromptInput maps queued entries to event.text and later injects the timestamp only when constructing ctx.Body, so the helper output is not reused as the next run's base prompt. (src/infra/heartbeat-runner.ts:669, 40be5ad58187)
• System event queue stores raw text, not enriched heartbeat bodies: enqueueSystemEvent trims and stores the provided text as event.text. There is no timestamp-refresh loop through this queue. (src/infra/system-events.ts:90, 40be5ad58187)
• Cron prompts embed user event text verbatim: buildCronEventPrompt concatenates pending event text directly into the reminder body. Replacing the first /^Current time:/ line would mutate user-authored reminder content, matching the regression called out in review. (src/infra/heartbeat-events-filter.ts:14, 40be5ad58187)
• Post-compaction path already avoids the helper entirely: post-compaction-context.ts now calls resolveCronStyleNow() directly and explicitly documents why substring-gating on "Current time:" is unsafe there, so the PR body overstates the helper's affected scope. (src/auto-reply/reply/post-compaction-context.ts:135, 40be5ad58187)

Review notes: reviewed against 40be5ad58187.