I have no idea how to recover from this state. pijul reset at least seems to do nothing at all. Maybe I’m using the wrong command.

saiko@invader ~/Src % pijul clone dblsaiko@ssh.pijul.com:pijul/pijul pijul1
Repository created at /Users/saiko/Src/pijul1
Downloading changes  [==================================================] 1053/1053 [00:00:24]
Applying changes     [==================================================] 1053/1053 [00:00:31]
Downloading changes  [==================================================] 1053/1053 [00:00:00]
Completing changes... done!
pijul clone dblsaiko@ssh.pijul.com:pijul/pijul pijul1  36.94s user 0.78s system 100% cpu 37.384 total
saiko@invader ~/Src % cd pijul1
saiko@invader ~/Src/pijul1 (pijul)-[main] % pijul channel new temp
saiko@invader ~/Src/pijul1 (pijul)-[main] % pijul reset --channel temp
Outputting repository... done!
Reset given paths to last recorded change
saiko@invader ~/Src/pijul1 (pijul)-[temp] % pijul diff -s
  (A bunch of "MV" lines)
saiko@invader ~/Src/pijul1 (pijul)-[temp] % pijul reset
[2024-03-22T21:33:11Z ERROR pijul] Error: "Refusing to reset, as there are unrecorded changes. Use --force"
Error: Refusing to reset, as there are unrecorded changes. Use --force
1 saiko@invader ~/Src/pijul1 (pijul)-[temp] % pijul reset -f
Reset repository to last recorded change
saiko@invader ~/Src/pijul1 (pijul)-[temp] % pijul reset   
[2024-03-22T21:33:20Z ERROR pijul] Error: "Refusing to reset, as there are unrecorded changes. Use --force"
Error: Refusing to reset, as there are unrecorded changes. Use --force
1 saiko@invader ~/Src/pijul1 (pijul)-[temp] % pijul diff -s
  (The same "MV" lines as before)

repeated.