Ask What They Were Trying to Do While the Terminal Is Open

ERR_DOCKER_OOM on auth login can mean the sample Compose file is too heavy, or that someone pointed a staging flag at a local daemon that was already dying. The stack is identical. The fix is not.

One question distinguishes them: what were you trying to do? Asked tomorrow in a survey, the answer is gone. Asked in the same terminal, it is a single sentence.

Do not open a survey. Do not ask for an email, a severity, and a product area. One line, skippable, stored next to the probe. If they press enter, you still have the stack.

Write the question in the developer's words. 'What were you trying to do?' beats 'Describe the business outcome you hoped to achieve.' They are in a hurry. Match that.

Twenty people saying 'log in to staging' against one error code is a broken path, not twenty tickets. Cluster on the code first, then read the sentences. The sentences tell you which doc heading to rewrite.

This is qualitative research you do not have to schedule. The session is the failure. You did not interrupt a happy path. You showed up when they were already stopped.

Do not let a model smooth the answer into corporate language before a human reads it. The draft GitHub issue should quote them. Your editor can tidy the title. The quote is the evidence.

AethelLayer asks that question and keeps it with the stack. You still decide whether the draft becomes an issue.