Could Not Dispatch 0.6.0

• A second card for a channel that reached the fallback because the provider was full.
  With Image or video when the provider is full set and an API key, a channel whose every
  source belongs to a provider account that was at its connection limit in the last 20 seconds
  gets that card, so it can say that every connection is in use; every other channel gets the
  usual one. Each fallback stream now points at the card with its channel,
  slate.ts?channel=<uuid>, rewritten by the next Apply or Cover new channels. Only these two
  cases are told apart: Dispatcharr does not tell a plugin why each stream failed, so a broken
  link and a passing outage look the same
  (#1, from
  @ckegels).
• A channel hidden from the output now goes back to its first stream like any other. The
  Dispatcharr channel list leaves hidden channels out unless asked, so such a channel stayed on
  the card until someone tuned away.

Commits

• 9aeaac5 CHANGELOG: 0.6.0 is released on 25 October
• 6289436 MEMORY: the hidden-channel trap and the bench with two cards
• 9fe6e70 Read hidden channels into the recovery catalogue
• 2eee36f Release 0.6.0
• d2b60b6 A second card for a channel that found the provider full
• 574b62a registry-pr: name the command that failed