feat(clients): add an "In 1 month" snooze preset

[mneuhaus]

The snooze menu stopped at "Next week", so parking a thread for longer meant typing a custom date.

What changed

• New preset In 1 month (matching "In 1 hour" and "In 3 hours"): wakes the thread on the same day one month later at 9:00, so Sep 29 wakes on Oct 29. The time column shows the date, e.g. "Oct 29 9:00".
• Days the next month lacks clamp to its last day: Jan 31 wakes on Feb 28, or Feb 29 in leap years. It never rolls into the month after.
• It is always at least 28 days out, so unlike "Next week" it never folds into another preset.
• The preset lives in packages/client-runtime (resolveSnoozePresets), so every entry point offers it:
  • web: the row hover menu, the thread context menu and bulk snooze;
  • mobile: the swipe/long-press snooze menu.
• The web wrapper formats the date with the user's clock preference.

Validation

• vp test run for Sidebar.snooze.test.ts and threadListV2.test.ts (mobile): 95/95. The new tests cover same-day wakes (including the last day of a month), the year rollover, and clamping for Feb, leap-year Feb and 30-day months.
• tsc --noEmit clean in client-runtime, web and mobile. Lint and format clean on the changed files.
• Not exercised in a real client; the change is one more menu entry built from the shared preset list.

Model: Claude Opus 5.5 in Claude Code (via T3 Code).

Rebased onto the new orchestrator (2026-10-02)

Rebased onto upstream main 8bc40b4, which includes pingdotgg#2829. It applied cleanly. The month-label test now checks the day of month instead of the English "May", because it failed on a German locale. Two upstream tests in the same file ("Mon" weekday) still fail on a German locale; they fail the same way on plain upstream.

🤖 Generated with Claude Code

[github-actions]

Thread transfer impact

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

This comment will update automatically after the next completed run.