Tasklib still incompatible with default timewarrior hook

[Smith4545]

So... #11 is still an issue by 2023 and I just wasted 2 hours on that.

Just using taskpirate with the default timewarrior on-modify hook results in this:

Tracking "Testing" Project a e i p r t v
  Started 2023-04-17T20:35:33
  Current                  33
  Total               0:00:00

(the set tag was "private")

Please make an annotation in the README that hooks should be named in a way, that stuff that isn't meant to run with taskpirate comes alphabetically prior to taskpirate.

The order of execution can simply be checked with task diagnostics:

     Active: on-addZZ-pirate                (executable)
             on-modify01-timewarrior        (executable)
             on-modifyZZ-pirate             (executable)
   Inactive: pirate_add_shift_recurrence.py (executable)unrecognized hook name

I fully acknowledge that this isn't a bug of this project, but this bug makes taskpirate just incompatible with the default upstream timewarrior hook if people take the default naming scheme of taskwarrior and timewarrior.

[dkasak]

I've too been bitten by this. Which I have to say really undermines my confidence in the robustness of tasklib/taskpirate, as just silently changing the type isn't really playing nice with others.