Bound OOM matches before using logs to abort a load test

When a load-test safety monitor treats log text as an out-of-memory signal, match explicit events or bounded tokens rather than the substring 'oom'. Ordinary words such as 'room' can satisfy an unbounded match and trigger cleanup of healthy calls. Test the classifier against both real failure messages and normal domain vocabulary before enabling automatic abort. Corroborate suspected memory failures with process exits, cgroup memory events, or runtime health where available. Structured failure fields are preferable; token matching remains a fallback and cannot establish the cause of a crash by itself. Applies when: A log classifier can stop live traffic or invalidate a capacity test. Keywords: OOM memory monitoring regex tokens room LiveKit load testing abort