task-manager v0.12.1

• A central store directory that cannot be read stops only the commands
  that resolve to that store. One such directory, for example a store at
  mode 000, stopped every command in every directory with no local .tasks/:
  each printed read central store <dir>: … permission denied and exited 1,
  also in the project of a healthy store. A command in the project of a
  healthy store now opens that store. A command in a directory that no store
  is registered for prints no .tasks directory found — run 'taskmgr init' to create one. A command in the project of the unreadable store, or one that
  names it with --store-name, prints the read failure as before.
  taskmgr store list shows the store with the health broken.
• tasks.Resolve returns the read failure of a central store only when
  that store owns the working directory or is named by
  ResolveOptions.StoreName. For every other directory it returned that
  failure too, so a front end that resolves at start-up could not reach
  tasks.Stores() to show the broken entry. It now opens the store that owns
  the directory, or returns ErrNoStore when none does. The entry that owns
  a directory still answers for it: Resolve does not fall through to the
  store of a shorter ancestor.