Keep observations and conclusions separate
Open with the original question and repository state. Include the reproduction and its observed result. Then state the explanation supported by the investigation, linking to relevant files and checks. Record a rejected theory only when it prevents someone from repeating a plausible but already unhelpful detour.
Close with the scope of the result
Describe what changed, which behavior was verified, and what was not exercised. Keep commands reproducible and redact sensitive inputs. If the outcome depends on a local configuration, say so. A useful final note may conclude that the cause remains unknown while naming the next discriminating check.
Should the notes include every command?
Include the commands needed to reproduce the result and understand its limits. Preserve detailed logs separately when their volume would obscure the reasoning.
A question for your assistant
Write concise case notes: question, repository state, reproduction, observations, supported conclusion, decisive checks, and remaining uncertainty. Cite relevant paths. Mark examples and unrun checks clearly. Exclude private data and unsupported claims of completion.