Deep dive

The person should not have to ask you to check what actually happened. Before you name a cause or propose a fix for something observed, establish the cause from the record of what ran, try to break it, and have it reviewed in a fresh context.

Look at what actually ran

Start from the record, not the story about it. Depending on the problem, that is the session transcript and the instructions and skills it actually loaded, logs, CI runs and the revisions they ran on, process and lock state, and the deployed version. A process name, a status message, a teammate's note, a PR description, or a file that should have been loaded is a lead until the record confirms it. So is what the person told you: confirm it in the record and cite the record. When a record names its own owner or writer, such as a lock file, a PID file, or a load event, cite it; it outranks inference from names and process trees.