feat(history): auto-expand commits on file navigation boundary

[fredrikaverpil]

Why?

When browsing repository history with :CodeDiff history, reaching the last file in a commit and pressing ]f wraps back to the first file of the same commit. This creates friction when reviewing changes across multiple commits.

What?

Auto-expand commits when navigating across commit boundaries:

• Navigate next (]f): At last file → expands next commit, selects its first file
• Navigate prev ([f): At first file → expands previous commit, selects its last file
• Boundary behavior: Respects cycle_next_file config — wraps around when enabled, stops with a warning when disabled

Implementation uses shared helpers:

• collect_commit_files: Recursively collects files (handles tree mode with nested directories)
• find_current_position: Locates commit/file indices for boundary detection
• update_cursor: Updates history panel cursor position

Also renames _load_commit_files to load_commit_files for consistency.

Notes

• Uses async load_commit_files with callback pattern for responsive UI
• Works with both list and tree view modes
• Uses user-configured keymaps (keymaps.view.next_file/prev_file)
• Existing navigation within expanded commits preserved

Recording

trimmed.mov

[esmuellert]

The idea is good, and currently we indeed can't automatically expand the commit and open files in it, but I might need to take some time to look at the PR and evaluate it

[fredrikaverpil]

@esmuellert I rebased on main and tidied up the implementation — unified the internal load_commit_files naming (dropping the _load_commit_files alias used by the refresh module) and resolved the merge conflicts. Also removed the POC caveat from the description; the implementation feels pretty good IMHO.

And I'm not sure what changed, but the cursor doesn't disappear off-screen anymore, as in my video recording above. It works/looks just as expected 🚀

[esmuellert]

@esmuellert I rebased on main and tidied up the implementation — unified the internal load_commit_files naming (dropping the _load_commit_files alias used by the refresh module) and resolved the merge conflicts. Also removed the POC caveat from the description; the implementation feels pretty good IMHO.

And I'm not sure what changed, but the cursor doesn't disappear off-screen anymore, as in my video recording above. It works/looks just as expected 🚀

Thanks for your continous work! I have been working on other features, but one of my proposed enhancements is supporting more fancy history view like a git merge history graph like we see in LazyGit. It requires major data structure (like DAG or tree) change to the commits list, so I would like to hold this change a bit. I will work on this feature soon. When I decide the new design, I might merge this one then work on it, or absort it in my changes.

[fredrikaverpil]

@esmuellert sounds great. Until then, I'll maintain this branch and rebase it from time to time.