Fixed regression that broke fuzzy matching for slash commands

[etraut-openai]

This addresses bug #7857 which was introduced recently as part of PR #7704.

[etraut-openai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Nice work!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[448523760]

Hi @etraut-opena Fuzzy match can cause a #7704 regression. To support both fuzzy matching and "/" history rollback, add a content-source flag to sync_command_popup (user input vs. history rollback). This is a significant change. And I did not make that change previous on #7704. Instead, i just made smallest change which by verifying the prefix between content and the pre-built commands

[etraut-openai]

@448523760, I'd like to get a fix for the fuzzy match regression in place. I think it impacts many more users than the other issue, which is pretty niche. You're welcome to address the other issue in a follow-up PR if you'd like.