>i'd say it's a bug. fossil could easily reserve some number of bits >of the qid (say 20 bits) to make the files in the dump unique >while still allowing space for a sufficient number of live files.
that's possibly closest to the intent of the qid discussion in intro(5), although it's not clear that considers the possibility of aliases within a hiearchy, where it might make more sense to have the Qid.path associated with the file, regardless of how you got to it. even so, for dump it's not been a big problem in practice only because one usually binds from the dump, not into it. i'm sure that somewhere it was suggested that high order bits of Qid.path should be avoided by file servers to allow for their use to make qids unique but i haven't been able to find that.