feat(tui): add prefix-filtered prompt history navigation

[avillagran]

• Implement filtered history navigation (Ctrl/Cmd + Up/Down) in the prompt input
• Preserve normal history behavior when not filtering
• Add a lightweight, runtime-free test helper for prompt history to avoid importing Solid in unit tests
• Update history store to delegate test factory to the helper
• Add unit tests for history navigation

Fixes: #9718

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate PRs Found:

1. PR Fix ctrl+p/ctrl+n navigation in multi-line TUI prompts #5473: "Fix ctrl+p/ctrl+n navigation in multi-line TUI prompts"

   • Fix ctrl+p/ctrl+n navigation in multi-line TUI prompts #5473
   • Likely related: Addresses control key navigation in TUI prompts, which overlaps with the Ctrl/Cmd + Up/Down navigation being added in PR feat(tui): add prefix-filtered prompt history navigation #9021

2. PR feat(tui): add inline Ctrl+R reverse-i-search for prompt history #6276: "feat(tui): add inline Ctrl+R reverse-i-search for prompt history"

   • feat(tui): add inline Ctrl+R reverse-i-search for prompt history #6276
   • Likely related: Another prompt history feature for the TUI that may have shared implementation details or test helpers for history navigation

3. PR fix(tui): resolve keybind conflicts and missing defaults (issue #4997) #8786: "fix(tui): resolve keybind conflicts and missing defaults (issue Keybinds #4997)"

   • fix(tui): resolve keybind conflicts and missing defaults (issue #4997) #8786
   • Possibly related: May address keybinding concerns that could conflict with or complement the new prefix-filtered navigation

[github-actions]

Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR.