Rune restrictions per unit of time and rune UX about lightning

[Amperstrand]

Highlightning the difference between AND vs OR

future_time=$(($(date +%s) + 24*60*60))
OR_restrictions='[["time<'$future_time'","rate=2"]]'
AND_restrictions='[["time<'$future_time'"],["rate=2"]]'
lightning-cli decode string=$(lightning-cli createrune restrictions=$AND_restrictions | jq .rune) | jq .restrictions

[
  {
    "alternatives": [
      "time<1715762646"
    ],
    "summary": "time (in seconds since 1970) less than 1715762646 (approximately 23 hours 59 minutes from now)"
  },
  {
    "alternatives": [
      "rate=2"
    ],
    "summary": "rate (max per minute) equal to 2"
  }
]

lightning-cli decode string=$(lightning-cli createrune restrictions=$OR_restrictions | jq .rune) | jq .restrictions

[
  {
    "alternatives": [
      "time<1715762646",
      "rate=2"
    ],
    "summary": "time (in seconds since 1970) less than 1715762646 (approximately 23 hours 58 minutes from now) OR rate (max per minute) equal to 2"
  }
]

Perhaps a safer way to create AND restrictions is to create hierarchical runes where the parent rune has a time to live ("time<'$future_time'") and the child rune has a rate limit.