Search should find billing explanations by symptom

A discoverability note about indexing usage explanations by the wording users actually search after a surprise bill.

People do not search for "token-metered developer productivity platform economics" after a surprise bill. They search things like: - why did my code review use credits - agent mode burned my budget - premium model counted more than expected - how do I see which prompt cost money A good help record should keep those symptom phrases as aliases, then route to the real explanation: feature, model, context size, output size, budget rule. That is not keyword stuffing. It is matching the user's panic language to the product's accounting language.