fissile 0.11.0

Added

• clean.sh at the repository root gives back the disk a checkout's builds
  took: it runs cargo clean, then removes every directory holding a valid
  CACHEDIR.TAG, such as a plan's scratch build under panta/. It is the clean
  verb ephor clean runs at the root of a branch checkout no live run holds.
  (PR #82)
• §FS-004-check-audit.2.2: an audit whose scan selects no files at all says
  so in one note on stderr, naming the directory it scanned and, inside a git
  repository, the repository root. A run from a directory the enclosing
  repository ignores no longer passes as a silent ok; stdout and the exit
  status are unchanged. (PR #84)
• §FS-004-check-audit.1.4: a staged soft finding's text detail separates the
  prior committed over-soft edits from the staged one (8 prior committed over-soft edits + 1 staged edit) and says when the prior edits had already
  reached the promotion limit; with incomplete history it reports at least N.
  The JSON fields are unchanged. (PR #83)

Changed

• §FS-003-exceptions.4: the refusal when two entries of one registry match the
  same overflow names the path of the first two colliding entries, in
  registry order, and says to remove or narrow the overlap, instead of naming
  only the registry and the measured file. Library break, forcing 0.11.0:
  ExceptionError::MultipleMatches gains a patterns: Box<[String; 2]> field,
  so code that constructs the variant or destructures it without .. stops
  compiling, and a caller comparing the exact message text must update.
  (PR #86)

Fixed

• §FS-004-check-audit.5: every spelling of the repository root passed to
  measure or check (., ./, src/.., the absolute path) is reported as
  the directory ., a file-level failure that still lets the other paths be
  measured, instead of an invalid argument or an empty path name.
  §FS-003-exceptions.3: exception add, retune and remove refuse an exact
  path that names the repository root and leave the registry untouched.
  (PR #85)