v6.3.0

Added

• assignment, conversation, feed and stop accept an agent work
  identifier, such as GH123-20260912-192458-assignment, to select that
  exact assignment or conversation instead of the newest at the issue.
  (#628)

Changed

• Scheduler failures now show one to a line, apart from the other
  instance facts, on the web home page and in dreamcatcher status. A
  failed GitHub read names its gh command without the options, such as
  gh issue list, rather than the whole command line.
  (#623)
• When a refresh fails, an assignment or conversation page now keeps its
  feed and shows a warning with the reason, as the home page already
  did. The warning clears once a refresh succeeds. The home page's
  warning now uses the same words.
  (#637)
• The assignment and conversation views list the other work of their
  kind at the issue, with each one's identifier, dispatch label and
  status, and stay on the work they opened on when newer work arrives.
  (#628)
• The upgrade instructions now say to stop every standalone view, such
  as dreamcatcher web or a refreshing status, before you install a
  release with a different state format, and to start the views again
  from the new installation. A view left running from the old format may
  show stale status. Upgrades that keep the state format need no such
  step. See
  Restart views across state formats.
  (#639)
• Looking up the work at one issue now reads only matching work
  directories, without opening unrelated records.
  (#640)
• The user stories clarify how request cards relate to saved work and
  which local-state failures need user repair. They also record that
  authorization to start work on another user's instance remains an open
  question, rather than an endorsed workflow.
  (#627,
  #632,
  #634)
• The README now directs ideas, suggestions and questions to GitHub
  Discussions, alongside the documentation link.
  (#642)

Fixed

• On Windows, a harness that cannot be started safely now errors its
  round and never runs.
  (#625)
• On a narrow web home page, a long status now moves below the issue's
  title and wraps within the row, instead of squeezing the title into a
  column of single characters.
  (#624)

What's Changed

• Share one conversation fixture between the terminal and web view tests by @alimanfoo in #621
• Clarify that cross-user dispatch authorization remains an open question in the stories by @alimanfoo in #627
• Update README by @alimanfoo in #642
• Show failed refreshes on assignment and conversation web pages by @alimanfoo in #637
• Link check passes locally but fails in CI when the remote uses an SSH host alias by @alimanfoo in #636
• Represent preparation, harness and finishing failures with distinct ending types by @alimanfoo in #629
• Select specific assignments and conversations from the terminal by @alimanfoo in #628
• Filter work directories before reading records for one issue by @alimanfoo in #640
• Clean up a Windows child when process containment fails by @alimanfoo in #625
• Record accepted handling of local-state failures in the user stories by @alimanfoo in #632
• A long status chip overflows its issue row on the home page by @alimanfoo in #624
• Improve aesthetics of scheduler failures by @alimanfoo in #623
• Clarify that standalone viewers must restart across state-format upgrades by @alimanfoo in #639
• Clarify request cards and existing agent work in the user stories by @alimanfoo in #634
• Prepare v6.3.0 release by @alimanfoo in #648

Full Changelog: v6.2.0...v6.3.0