Recurrence task template self-deletes

[OptimisticLock]

To report a bug...

• What command(s) did you run?

$ task add +test hello  due:yesterday+3h wait:yesterday+3h until:5pm recur:14days
Created task 408 (recurrence template).

$ task +test hello all

ID  St UUID     Age   Done Tags R Wait  Due        Until Description
409 P  8360d6a8 27s         [1] R       2024-01-29 22h   hello
410 W  19de5cdf 27s         [1] R 12d   2024-02-12 22h   hello
408 D  6e4a4824 32s      -  [1] R       2024-01-29 22h   hello
Task 408 'hello' expired and was deleted.

• What did you expect to happen?

I was expecting task 408 to have status R.

• What actually happened?

Template expired?

• Paste the output of the task diag command.

task 2.6.2
   Platform: Linux

Compiler
    Version: 9.4.0
       Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64
 Compliance: C++17

Build Features
      CMake: 3.16.3
    libuuid: libuuid + uuid_unparse_lower
  libgnutls: 3.6.13
 Build type: release

Configuration
       File: /home/ira/.taskrc (found), 4430 bytes, mode 100644
       Data: /home/ira/.task (found), dir, mode 40755
    Locking: Enabled
         GC: Enabled
     Server:
         CA: -
Certificate: -
        Key: -
      Trust: strict
    Ciphers: NORMAL
      Creds:

Hooks
     System: Enabled
   Location: /home/ira/.task/hooks
     Active:
   Inactive: 8981.json (not executable)unrecognized hook name

Tests
   Terminal: 200000x46
       Dups: Scanned 576 tasks for duplicate UUIDs:
             No duplicates found
 Broken ref: Scanned 576 tasks for broken references:
             No broken references found