Spurious errors when pushing to Share after moving a sub-namespace

[anovstrup]

Steps to reproduce:

1. Add a term in a sub-namespace (e.g., unique ability X = X Nat)
2. Push to Share (push)
3. Move the sub-namespace (e.g., move.namespace X Y.X)
4. Push to Share (push). A "There are some changes at [namespace] that aren't in the history you pushed."
5. Pull from Share (pull). "Nothing changed [...]"
6. Push to Share (push). Works!

Actual output looks like this:

._my_shared.scratch> push anovstrup.public.tmp       

  Uploaded 0 entities.


  ❗️
  
  There are some changes at anovstrup.public.tmp that aren't in the history you pushed.
  
  If you're sure you got the right paths, try `pull` to merge these changes locally, then `push`
  again.

._my_shared.scratch> pull anovstrup.public.tmp

  Downloaded 0 entities.


  Nothing changed as a result of the merge.

._my_shared.scratch> push anovstrup.public.tmp

  Uploaded 6 entities.


  View it on Unison Share: https://share.unison-lang.org/@anovstrup/code/latest/namespaces/public/tmp

[ceedubs]

Wow good sleuthing, @anovstrup! Thank you for minimizing this!

[anovstrup]

😁 @ceedubs Just dumb luck — I happened to have just run into this after only moving a namespace since my previous push.