Sometimes one want to create a repository db <b>within</b> the directory that also will hold the checkout. Especially if you are com from other VCSs like e.g. Git or Darcs. I do the same, if I have a whole worktree for that I want to create an one-shot repository within.

But if I ask Fossil to remove all unknown files via <tt>clean --all</tt>, it will remove its own database that the current checkout was taken from. For example:
<pre>
  mkdir test1
  cd test1
  fossil new myrepos
  fossil open myrepos
  fossil add ...
  fossil commit
  :
  :
  fossil clean --all
</pre>
Oops, my repository is gone!

I would expect, that -- at least -- every repository, that the current checkout was taken from, should be considered as a known file and should not be subject to 'clean'. Perhaps -- as a kind of loyality -- fossil should overlook all fossil repository db it ever encounter during its traversal?