Example: Search for “unrecord”, Returns the following items. Here I have sorted them, so you can see the many duplicates; the actual output list is apparently not sorted, or unclear by what attribute.

#127 Ability to `pijul rec --amend` a change with dependents
#128 `git rebase` function-a-like?
#298 Feature Discussion: Mercurial like *topics*
#338 [Crash] After `pijul fork --change <hash> <name>` and `pijul channel switch <name>`
#342 [Feature request] Tools to deal with spurious dependencies.
#625 push/pull patch order mismatch
#626 consider making 0/0 progress bar look complete
#627 rename `unrecord` to `unapply`
#627 rename `unrecord` to `unapply`
#667 Crash finding pending changes when pulling
#668 apply (or push or pull) should be able to fail when a conflict occurs
#669 [BUG] Applying patches that remove all lines from a file
#674 re-record dependencies after unrecord, and reverting patches
#674 re-record dependencies after unrecord, and reverting patches
#675 Bringing back unrecorded patches
#675 Bringing back unrecorded patches
#677 push and pull command output needs more detail
#682 Another round of Clippy fixes
#688 Make pijul reset safer
#690 how do you list changes that depend on a change?
#694 Calculating number of patches since a tag
#698 [UNRECORD] sometimes tracked files not modified
#698 [UNRECORD] sometimes tracked files not modified
#723 `pijul push`: No such file or directory
#724 `pijul apply` Causes Destructive Loss of Unrecorded Changes
#724 `pijul apply` Causes Destructive Loss of Unrecorded Changes

Yes, I’m working on a more general fix for the Nest (I want to fix the entire Nest, not just this issue ;-)). I’m leaving this open since it is an important point.