fix(web): a snoozed thread wakes in the open chat view

[juliusmarminge]

With a snoozed thread open, the "Snoozed" status line didn't switch to "Woke from snooze" at the wake time, and the wake timer re-fired every 50 ms until something else changed the thread.

The React Compiler caches ChatView's effectiveSnoozed(shell, { now: new Date() }) and threadWokeAt(...) results on the thread shell and supportsSnooze, so the clock read during render froze. The timer's tick only re-ran the effect. The cached check still said "snoozed", so the timer re-armed with the 50 ms minimum, over and over. I confirmed this by compiling ChatView.tsx and reading the cache guards on those two expressions.

The snooze clock is now state. It resets when the shell changes and advances when the wake timer fires, so both checks re-run with a real time. The compiled output now guards them on snoozeClock.

The mobile thread list had the same bug (#20967, found by the on-device render counter in #21001).

Checks: lint and typecheck on ChatView.tsx, and reactCompilerCoverage for ChatView.tsx. No test covers the snooze status line, and I haven't checked it in a browser.

Claude Opus 5.5 via Claude Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 1a9e5e0

Macroscope's review found this PR approvable — This is a focused one-file bug fix that makes the existing snooze wake timer update the clock used by the open chat view, so status transitions occur without repeatedly rearming the timer. It introduces no schema, deployment, default, or broader product behavior changes.

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