[callumalpass]

Fixes #2521.

Problem

#2441 (4.16.0) made the Next status of the first completed status also reset a recurring series' status after each completed or skipped occurrence. There was no separate switch, so any setup that already had a Next status on Done got the reset. That's common: setting Done → Next status to an inbox or default status is how reopening a task is configured.

The reporter's setup matches: custom statuses (inbox, do-next, calendar, …), a recurring task at calendar. Completing it with a status click on a Kanban card, or with Mark complete or skip → Completed on schedule, both reach TaskService.toggleRecurringTaskComplete, which rewrote status to Done's Next status. The edit modal's Completions calendar writes complete_instances directly and never ran this code, which is why that path kept the status.

On main it's worse: #2492 (unreleased) gates the recurring status-click cycle on the same Next status, so a Kanban click on the reporter's task would move it calendar → waiting without completing anything.

Fix

• New setting Reset status after each occurrence (Features → Recurring tasks), resetRecurringStatusAfterOccurrence.
  • On in DEFAULT_SETTINGS, so new setups keep the feat: optionally reset a recurring task's status after each occurrence #2441/feat: let recurring tasks follow the status cycle on click #2492 behaviour, including built-in Done → Open.
  • migrateLoadedSettingsData loads it as false when saved settings don't have it, so existing setups keep their recurring statuses.
• TaskService.getStatusAfterOccurrence and the feat: let recurring tasks follow the status cycle on click #2492 click cycle in taskCardActions both check it.
• Translations added for all locales. Docs and the release note are updated. The note tells anyone who set Done's Next status on purpose to get the reset to turn the setting on.

Tests

• e2e/issues/issue-2521-recurring-status-reset.spec.ts uses the reporter's statuses (Done → inbox, default inbox) and a task at calendar, every 2 days, anchored on scheduled. It covers a Kanban status-dot click and the context-menu Completed on schedule: both fail on main (status inbox, and the click doesn't complete) and pass with the fix. A third case checks that the reset still applies when the setting is on.
• The existing feat: optionally reset a recurring task's status after each occurrence #2441 and feat: let recurring tasks follow the status cycle on click #2492 e2e specs now turn the setting on, and pass (9/9 across the three specs, Obsidian 1.15.0 under xvfb).
• Unit tests: TaskService keeps the status with the setting off; the status click completes in one click with it off; settings migration (saved data → off, new setup → on).
• Full Jest suite (6045 passed), lint, typecheck, build, i18n:check, test:i18n-source, check-docs and the bundle-size check all pass locally.