v9.4.0

Changed

• The dreamcatcher.toml that dreamcatcher init writes names each
  dispatch label after the kind of work that it asks for, not after the
  skill that its route runs: agent-conversation in place of
  dream:scout, agent-assignment in place of dream:smith,
  agent-assignment-easy in place of dream:less and agent-campaign
  in place of dream:lead. Each route's prompt still invokes the same
  skill. init leaves an existing dreamcatcher.toml alone, so a
  repository that already has one keeps its labels. To switch such a
  repository to the new names, rename each label on GitHub, where an
  issue keeps its label through the rename. Then rename the route's
  label in dreamcatcher.toml to match, commit and push the file, and
  restart the daemon. Rename a conversation or campaign label only when
  none of its conversations or campaigns is open, because an open one
  pauses when its label is renamed. An open assignment is unaffected, as
  the user renames a dispatch label
  tells. (#820)

Fixed

• A dispatch label that the user applied still counts as theirs after
  the label is renamed on GitHub. Before, every issue that carried the
  label when it was renamed showed its request as held, with the label
  applied by an unknown account. A label that GitHub shows before it
  records who applied it now shows that the update cannot tell who
  applied it, where before it showed as applied by an unknown account.
  (#819)

What's Changed

• A renamed dispatch label reads as applied by an unknown account by @alimanfoo in #819
• Name the default dispatch labels after the kind of work, not the skill by @alimanfoo in #820
• Prepare the v9.4.0 release by @alimanfoo in #824

Full Changelog: v9.3.0...v9.4.0