When a developer changelog tracker grows, index cost becomes the architecture constraint. Re-embedding every page on every deploy is wasteful, while a single giant query makes the bot slow and hard to explain. Short answer: use staged retrieval with explicit collections, bounded queries, and source context that survives every step. Start with a small candidate set, then rerank or expand only when the question needs it. The before-and-after mental model The fragile design is ea...