doc: recommend injectpaymentonion in place of sendonion.

Among other things, injectpaymentonion insists on knowing the destination
amount_msat.

Signed-off-by: Rusty Russell <[email protected]>

Author: rustyrussell

contrib/msggen/msggen/schema.json

@@ -21942,7 +21942,7 @@
                       "amount_msat": {
                         "type": "msat",
                         "description": [
-                          "The amount of millisatoshi we intended to send to the destination."
+                          "The amount of millisatoshi we intended to send to the destination.  This can only be missing in the case of someone manually calling sendonion without the `amount_msat` parameter (which no plugin currently does)."
                         ]
                       },
                       "amount_sent_msat": {
@@ -24449,7 +24449,7 @@
                 "amount_msat": {
                   "type": "msat",
                   "description": [
-                    "The amount delivered to destination (if known).  This is not known in the case where sendonion(7) was used to initiate the payment without the `amount_msat` parameter."
+                    "The amount delivered to destination (if known).  This is not known in the case where sendonion(7) was used to manually initiate a payment without the `amount_msat` parameter."
                   ]
                 },
                 "destination": {
@@ -29732,6 +29732,7 @@
       "rpc": "sendonion",
       "title": "Send a payment with a custom onion packet",
       "description": [
+        "Note: you probably want to use the more modern and flexible `injectpaymentonion` command instead of this.",
         "The **sendonion** RPC command can be used to initiate a payment attempt with a custom onion packet. The onion packet is used to deliver instructions for hops along the route on how to behave. Normally these instructions are indications on where to forward a payment and what parameters to use, or contain details of the payment for the final hop. However, it is possible to add arbitrary information for hops in the custom onion, allowing for custom extensions that are not directly supported by Core Lightning.",
         "",
         "If the first element of *route* does not have \"channel\" set, a suitable channel (if any) will be chosen, otherwise that specific short-channel-id is used. The following is an example of a 3 hop onion:",
@@ -30057,6 +30058,7 @@
         "Christian Decker <<[email protected]>> is mainly responsible."
       ],
       "see_also": [
+        "lightning-injectpaymentonion(7)",
         "lightning-createonion(7)",
         "lightning-sendpay(7)",
         "lightning-listsendpays(7)"

doc/schemas/sendonion.json

@@ -4,6 +4,7 @@
   "rpc": "sendonion",
   "title": "Send a payment with a custom onion packet",
   "description": [
+    "Note: you probably want to use the more modern and flexible `injectpaymentonion` command instead of this.",
     "The **sendonion** RPC command can be used to initiate a payment attempt with a custom onion packet. The onion packet is used to deliver instructions for hops along the route on how to behave. Normally these instructions are indications on where to forward a payment and what parameters to use, or contain details of the payment for the final hop. However, it is possible to add arbitrary information for hops in the custom onion, allowing for custom extensions that are not directly supported by Core Lightning.",
     "",
     "If the first element of *route* does not have \"channel\" set, a suitable channel (if any) will be chosen, otherwise that specific short-channel-id is used. The following is an example of a 3 hop onion:",
@@ -329,6 +330,7 @@
     "Christian Decker <<[email protected]>> is mainly responsible."
   ],
   "see_also": [
+    "lightning-injectpaymentonion(7)",
     "lightning-createonion(7)",
     "lightning-sendpay(7)",
     "lightning-listsendpays(7)"