79c3b994cf60ab22ec75a776b3048bc80179af74
A nudge could only be deferred from Telegram or the web UI. The voice path had no route to store.ResolveNudge at all, so the channel she nudges on hardest was the one he could not answer out loud. resolveSnooze runs pre-route, right after the quiet toggle, and writes the same `snoozed` outcome the buttons write — which also drops the row out of RepeatUnacked, so a deferred sev4 stops re-sending every five minutes. The window is what makes this safe to run before the router. "потом" is an ordinary word; it only counts as a deferral when a pending nudge was sent in the last twenty minutes, and otherwise the turn routes normally. Single word patterns still match single-word utterances only, so "потом схожу за водой" reports a plan instead of silencing the rule that prompted it. Channel is not filtered: a nudge that went to Telegram is still what he is answering when he says "потом" at the microphone. QA-PLAN gains the two new manual checks and drops the 319 warning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TrVSBKe3RFDF4fGYKWYQnX
Description
No description provided
Languages
Go
97.1%
HTML
0.9%
Shell
0.6%
CSS
0.5%
Makefile
0.3%
Other
0.6%