Need to flag "use to" when "used to" is intended

### The correct phrase to use when talking about a past habit is "used to" with "used" in the simple past tense.

- Cline **use to** be able to doc in it's own separate window. ❌
- it's the way we **use to** do it - as it's a matter of preference ❌
- Normally I **use to** develop with objects in JS ❌
- I **use to** see my workspace flow and now I don't ❌
- You **use to** know when what you shipped was solid, now you just know it passed the tests - big difference. ❌

### The same phrase is used after forms of "to be" and "to get" to mean "accustomed to".

- If you are **use to** Ubuntu, then the way sudo works should not is not strange. ❌
- im pretty new to vim helix way of typing and im getting **use to** it slowly ❌
- I've tried to get **use to** the tabs.... but it it's bad enough that it makes me want to leave for another product ❌
- I wasn't **use to** doing a lot of work and studying in high school ❌
- so I'll give it some time to get **use to** and then see about making a feature request ❌
- I'm sure I will get **use to** it and enjoy it more when I am using the pods ❌
- Issues labeled as such are a good way to get **use to** the codebase. ❌
- I think it'll take time but people will get **use to** it. ❌
- this key binding is important and we really got **use to** it ❌
- However it is a challenge to began getting **use to** the keyboard when navigating VSCode ❌

### The phrase "use to" can occur in many other contexts. These must not be flagged:

- What compiler did you **use to** build your app? ✅
- LiteLLM, which we **use to** talk to LM Studio, requires this interpreter.llm.api_base ✅
- .xpi files that you can **use to** install it in your browser are available ✅
- Look to the creators of the terminal emulator you **use to** fix these issues if the previously mentioned fixes don't work for you. ✅
- Here are some of the hack I **use to** make my life working on the command line a bit easier. ✅
- you can add rules that the endpoint will **use to** allow or disallow user's connections ✅

### Passive constructions

While looking for the above examples I discovered that another very common mistake is to write "use to" instead of "used to" in normal passive constructions that are not either of the idioms mentioned above:

- It is **use to** mitigate issues with prompt poisoning ❌
- This is **use to** host fragment. ❌
- Which method is **use to** send messages? ❌
- This script is **use to** fetch all the branches from all the repositories in the current directory ❌
- In printing Prefix and escape predicates are **use to** perform validation and drive the logic of printing. ❌

No file or test is named. Start by finding the existing rule implementations and their tests for phrase and context matching, then run the relevant test suite to understand how false positives are recorded. Done means flagging habitual, accustomed-to, and passive “use to” cases while leaving the listed legitimate constructions unflagged.

Written by the indexing model from the issue text.