For the same developer on the same branch, Claude follows the repository's logging convention in some sessions and ignores it in others. The convention's text hasn't changed in weeks. What is the best first step?

Answer: D — Run /memory in an affected session to check which memory files are actually being loaded

/memory shows which memory files are loaded in the current session, which is how you diagnose behavior that differs between sessions. A common finding is that the convention sits in a directory-level file that only applies in one subtree, or in a file that isn't where you expected. (A) and (B) change content before confirming it's loaded, and (B) creates copies that will drift. (C) makes an always-on convention depend on manual invocation.