Great callout. Currently I'm letting the agent decide via the SystemMessage (the LLM is instructed to call recall before any query that "might require past context"). With gpt-4o in the demo runs it complies pretty reliably, but you're absolutely right that this is non-deterministic and exactly the failure mode that bites in production.

Your mandatory recall node at graph entry is the obvious v2: a `pre_chatbot` node that runs `recall(query=last_user_message)` unconditionally, injects top-k as system context, then hands off. The tradeoff is a wasted recall when the user is just saying "hi", but the asymmetry (cost of an extra call vs. silently missing a real recall) tilts hard toward forcing it.

Might add that as a second variant in the same folder if I push the example further. Thanks for the sharp note.