fix(web): time-based labels update under the React Compiler

[juliusmarminge]

The React Compiler caches render-time expressions on the reactive values they read. A clock read inside one of those expressions (formatRelativeTimeLabel(at) with its Date.now() default, or canSnooze(thread, { now: new Date().toISOString() })) freezes until those other inputs change. react/purity misses these because the clock sits in a default argument or an object literal. Same class as #20967 (mobile) and #21019 (ChatView).

Fix. Relative-time labels render through a new RelativeTime component built on useRelativeTimeState, so each label re-renders only when its text changes. Scheduled-task labels (relativeLabel also formats future times) take the useNowMinute tick as an explicit clock. This replaces two parent useRelativeTimeTick(60_000) calls whose re-renders never reached the memoized rows. The sidebar row's snooze gate gets the #20967 / #21019 treatment: its clock is state, reset when thread changes and advanced by a timer at the queued-turn grace expiry.

I checked every site by compiling the file with oxc-transform-react and reading the $[n] !== guard around the clock read.

Site	Frozen	Visible bug	Fix
Sidebar.tsx:1859 row canSnooze gate	yes, on thread	After a message, the snooze button stays hidden past the 2-minute queued-turn grace until the thread changes	clock in state + expiry timer
ScheduledTasksSettings.tsx:615 "Next run in 5m"	yes, on task.nextRunAt	Countdown never moves; parent tick re-renders, memoized row doesn't	ScheduledRelativeLabel (useNowMinute)
ScheduledTasksSettings.tsx:733,780 webhook delivery "5m ago"	yes, on deliveries	stale age	same
ThreadAutomationsPanel.tsx:172 "next in 5m"	yes, on panel inputs	stale countdown	same
PullRequestListRow.tsx:99 updated age	yes, on updatedAt	stale age	RelativeTime
PullRequestTimelineTab.tsx:223,330,391,432,486	yes, on event.at	stale ages	RelativeTime
PullRequestSummaryTab.tsx:107, PullRequestReviewAnnotation.tsx:269 comment ages	yes	stale ages	RelativeTime
PullRequestDetailPanel.tsx:2343,2514 updated age	yes, on detail (live refresh ≥5 min, and an unchanged PR keeps the same object)	stale age	RelativeTime
PullRequestLinkPreview.tsx:142, PullRequestGhosts.tsx:206	yes	stale age	RelativeTime
ThreadPullRequestsPanel.tsx:184,379 linked / "synced 5m ago"	yes, on link.linkedAt / thread.pullRequests	stale age	RelativeTime
LegacySidebar.tsx:877 row age	yes, on thread timestamps	stale age (legacy sidebar)	RelativeTime
SettingsPanels.tsx:3513,3515 archived/created ages	yes, on the archive list	stale ages	RelativeTime
DiagnosticsSettings.tsx:1185,1213,1241,1287 trace ages	yes, on data	stale ages between manual refreshes	RelativeTimeNoWrap (useRelativeTimeState)
ComposerStashMenu.tsx:208 stash age	yes, on entries	reopening the menu shows the age from when the stash last changed	RelativeTime
PreviewRecentUrlCard.tsx:22 visited age	yes, on lastVisitedAt; its bare useNowMinute() re-rendered without busting the cache	stale age	RelativeTime
Sidebar.tsx:1061 snooze presets	yes, but open is a dep, so it recomputes on every open	none	checked
Sidebar.tsx:583 partitionSidebarThreads	cached on nowMinute + wake tick	none	checked
Sidebar.tsx:4816 snooze wake label "5m"	cached in the list block, which includes snoozeNow (minute + wake tick)	none	checked
Sidebar.tsx:826 RelativeTimeLabel	cached on nowMinute	none	checked
ChatView.tsx snooze/woke	owned by #21019	—	not touched
ChatView.tsx:5194,5203 "Snoozed, 5m left" / "Settled 5m ago"	cached on nowMinute	none	checked
MessagesTimeline.tsx formatDayAwareTimestamp (3 sites), formatUpcomingTimestamp reset	cached on timestamp	only flips "today"→"yesterday" at midnight	left; see below
StorageSettings.tsx:314 last run	CleanupSection builds summaries outside any guard; its own minute tick re-runs it	none	checked
ConnectionsSettings.tsx:723,943, UsageLimits*.tsx	clock passed explicitly from a ticking nowMs / limitsNow	none	checked
WelcomeWizard.tsx:1722 last active	yes, on lastActiveAt	onboarding import list, open for seconds	left
MessagesTimeline.tsx:3308 WorkingTimer	initial text only; the interval writes textContent	none	checked
SidebarUpdateCapsule.tsx:32, useRelativeTimeState.ts:30	useSyncExternalStore snapshot closures	none	checked
CustomSnoozeDialog, useThreadActions, useThreadActionMenu, useComposerTypingGuard, useReviewGuideWriter, UsageLimitRecoveryBanner, GitActionsControl, WorktreeSetupCard, SshPasswordPromptDialog, _chat.pull-requests, ChatComposer, HtmlRenderFrame, McpAppFrame, AttachmentFilePreview, toast, ProviderUpdateEnvironmentRows	reads in handlers, effects, state initializers, or atoms	none	checked

Left.

• MessagesTimeline day-aware message timestamps keep their day bucket until the row re-renders, so a message from 23:59 still says "11:59 PM" instead of "yesterday at 11:59 PM" after midnight. Fixing it needs a day tick per row in a hot list. I'd rather not add that without measuring.
• CommandPalette.logic.ts:350 formats thread ages while building the item list. The palette rebuilds when it opens, so it's fine in practice.
• WelcomeWizard last-active age (see table).

Verified: lint and tsc-rs on apps/web, reactCompilerCoverage for every changed file, and Sidebar.snooze / Sidebar.logic / pullRequestListLines tests. No browser pass.

Claude Opus 5.5 via Claude Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 2f03af4

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that makes existing relative-time labels and the existing snooze gate respond to elapsed time under the React Compiler. The changes add bounded timer-driven updates without changing schemas, integrations, defaults, or sensitive functionality.

^{You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for bd811b4.

This comment will update automatically after the next completed run.

[coderabbitai]

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}