v9.1.0

Changed

• A lead round's trigger says that a sub-issue handed back and that
  its pull request changed, where it said handback and pull
  request.
  (#777)
• The daemon stops when an update cannot complete, for example because a
  record under .dreamcatcher/ is damaged or a write fails. It prints
  the file and what is wrong with it, ends its rounds and its web page
  as Ctrl-C does, and leaves the record of the last complete update in
  place. Fix the cause and start the daemon again, and the interrupted
  work carries on. The daemon used to report the failure and try again
  at every update, and a conversation or campaign whose own records
  could not be read showed the failure on its row.
  (#773)
• An open page whose refresh gets no answer from the server, as when the
  daemon has stopped, keeps what it shows and warns "Refresh failed.
  Check the terminal running dreamcatcher." It used to show no warning.
  (#773)
• Each card and request row on the web home page keeps GitHub's
  information at its top and dreamcatcher's at its bottom.
  (#770)
• An ended assignment's card on the web home page says "completed" or
  "cancelled" once, where it said "ended", and every ended card's title
  is quieter.
  (#779)
• A pull request that is ready for review now shows in brighter text
  than a draft, on an assignment's card and on its page. In the matrix
  theme, every other pull request now shows in the subdued text.
  (#780)
• An assignment whose pull request is merged or closed, and whose
  wrap-up round has yet to start, is waiting "awaiting wrap-up", where
  it said that the pull request is merged or closed.
  (#766)
• A campaign's sub-issue with no assignment and no request shows only
  its number and title on the web page, without the "no assignment" line
  and the open or closed badge.
  (#764)
• The first example in the configuration guide includes a campaign
  route, so it shows each kind of route the guide describes.
  (#775)

Fixed

• On the web page, a lead round that names its sub-issues lists its
  trigger and timing beside its number, on separate lines, as every
  other round does.
  (#777)
• A wrap-up round that finishes as the user cancels its assignment
  leaves the assignment cancelled, so its worktree, branch and
  uncommitted work stay the user's. A cancel that comes after the
  wrap-up round changes nothing, and dreamcatcher cancel says that the
  assignment has already ended.
  (#774)

What's Changed

• Update the triage guidance from the 23 October triage session by @alimanfoo in #719
• Awaiting wrap-up by @alimanfoo in #766
• Show only the title for campaign sub-issues with no assignment or request by @alimanfoo in #764
• Give frozen dataclass collection fields one read-only type by @alimanfoo in #765
• Build the server in a slow web test the way the product does by @alimanfoo in #772
• Group GitHub information at the top of each home card by @alimanfoo in #770
• Give each duplicated test helper one home by @alimanfoo in #767
• Realign local dreamcatcher config for this repo with the default config by @alimanfoo in #776
• Add campaign route to configuration example by @alimanfoo in #775
• Stop the daemon when a scheduler update cannot complete by @alimanfoo in #773
• A wrap-up round can record completion over a cancel, and its worktree is then removed by @alimanfoo in #774
• Appearance of completed assignments by @alimanfoo in #779
• Round info ergonomics by @alimanfoo in #777
• Differentiate PR draft versus ready by @alimanfoo in #780
• Prepare the v9.1.0 release by @alimanfoo in #783

Full Changelog: v9.0.0...v9.1.0