CLI - changes in recurrent transfer functionality after HF

Updated after meeting 26.11.25

create

1. clive process transfer-schedule create -h - update help

2. I think we don't need to change the behavior in clive process transfer-schedule create. If the user doesn't specify --pair-id, 0 is used as the default value.

3. If the user wants to create a second recurrent transfer without specifying --pair-id and there is a transfer with --pair-id=0, an error occurs.

The error message should be updated:

A scheduled transfer to bob with pair_id 0 already exists.   
If you want to create a new recurrent transfer to bob, use the command clive process transfer-schedule create and specify the --pair-id.     
If you want to modify an existing one, use `clive process transfer-schedule modify`.   
If you want to list the existing recurrent transfers, use `clive show transfer-schedule`.

modify

4. clive process transfer-schedule modify -h - update help

5. Modify -the behavior should be changed.

Now:
If the user doesn't specify --pair-id, Clive tries to modify the transfer with --pair-id =0 (even if there is only one transfer)

Should be:
a. If there is only one transfer schedule and its pair-id is 0, then Clive modifies it without requiring pair-id.
b. Otherwise (also if there is only one transfer schedule, but its pair-id differs from 0), then the error should be raised.

remove

6. clive process transfer-schedule remove -h - update help

7. Similar as in case modify.

Now:
If the user doesn't specify --pair-id, Clive tries to remove the transfer with --pair-id =0 (even if there is only one transfer):

Should be:
Should be:
a. If there is only one transfer schedule and its pair-id is 0, then Clive removes it without requiring pair-id.
b. Otherwise (also if there is only one transfer schedule, but its pair-id differs from 0), then the error should be raised.