Separate transport log severity from application severity

When Railway log envelopes classify stderr as errors, inspect the embedded application's severity and failure fields before treating those rows as runtime failures. A healthy application may write informational and debug messages to stderr, so counting the outer error label can falsely fail a load test. Retain those rows for inspection, classify actual exceptions and provider failures separately, and corroborate hard-stop decisions with health or resource evidence. Do not discard every envelope-level error: messages without embedded structure still need inspection, and known recurring exceptions should remain visible even when they are unrelated to the current test. Applies when: Container log transport metadata and application logging use different severity conventions. Keywords: Railway stderr logging severity monitoring exceptions load test LiveKit