Practice — Memory Systems for LLM Applications (5 questions)

You're building a coding agent that works on the same handful of client repositories across many sessions over several weeks. Users report three complaints:

1. It forgets project-specific conventions between sessions (build commands, "never touch this legacy directory") and has to be re-told every time.
2. On a repo it has worked in before, it sometimes re-proposes a fix that was already tried and already failed, for the same bug class.
3. On long single-session tasks, it occasionally loses track of the multi-step plan it made at the start, after many tool calls.

For each complaint, identify which memory layer is missing or misdesigned, what should be stored, and whether it should be loaded eagerly or retrieved on demand. Then explain how the three fixes are different from each other, not just "add more memory."