The files under scenarios/issues/ preserve selected protocol shapes described in upstream reports. Their names provide traceability; they do not prove that FaultCam recreated the reporter's camera, firmware, network, or product failure.
An exact reproduction would require, at minimum, the original device or an authoritative wire capture, the affected client/relay version, matching configuration, a client-visible failure signature, and a control run showing the corrected behavior. None of the three checked-in issue scenarios currently meets that complete standard.
| Upstream label | Local scenario | What is represented | Current defensible conclusion |
|---|---|---|---|
| MediaMTX #5949 | mediamtx-5949-oversized-origin.yml |
Raw SDP with the recorded oversized numeric o= fields. |
Issue-inspired input shape only. The current MediaMTX integration uses a reconnect scenario, not this issue file. |
| go2rtc #2232 | go2rtc-2232-basic-digest.yml |
A Hikvision-like mount and fixed Basic-plus-Digest realm/nonce/credentials. | Issue-inspired authentication shape only. The original firmware and exact challenge ordering are unavailable. |
| go2rtc #2202 | go2rtc-2202-missing-sps-pps.yml |
H.264 with parameter sets omitted during startup. | Issue-inspired missing-parameter-set shape only. It is not a Tapo firmware or proxy clone. |
These three files have no assertions and are not among the 37 registered regression_* CTest executions (5 normal/authentication/SDP plus 32 action-or-alias oracles). faultcam inspect can prove that they parse; it cannot prove a named upstream issue.
Related core mechanisms do have independent regressions:
regression_sdp_boundary_origin;regression_basic_digest_dual_challenge;regression_missing_parameter_sets.
Those tests prove FaultCam's controlled protocol behavior and the strict probe's observations. They still do not prove the upstream product bug.
The commands below generate new local reports with fixed FFmpeg 8.1.2. They are mechanism checks, not issue verdicts:
ffmpeg -version
.\build\Release\faultcam.exe run `
--scenario scenarios\issues\mediamtx-5949-oversized-origin.yml `
--json artifacts\issues-current\mediamtx-5949.json --timeout-ms 15000 -- `
ffmpeg -nostdin -hide_banner -v error -rtsp_transport tcp `
-i "{rtsp_url}" -t 2 -map 0:v:0 -f null -
.\build\Release\faultcam.exe run `
--scenario scenarios\issues\go2rtc-2232-basic-digest.yml `
--json artifacts\issues-current\go2rtc-2232.json --timeout-ms 15000 -- `
ffmpeg -nostdin -hide_banner -v error -rtsp_transport tcp `
-i "{rtsp_url}" -t 2 -map 0:v:0 -f null -The missing-parameter-set file may legitimately make a decoder fail. Because the file currently declares no expected client result, that failure must not be reclassified as PASS after the fact. Add a purpose-built assertion and client oracle in a separate reviewed regression before making a behavioral claim.
No fresh artifacts/*-current issue-specific result was found during the 2026-07-26 documentation audit. The old files under artifacts/final/ are not reused for current conclusions. Therefore the current status of all three named issue reproductions is not proven.
When evidence is added, record the exact client version, scenario/media hashes, command, raw client output, declared expectation, cleanup, and whether the conclusion is exact or merely inspired. A container start, an event-name match, or an undeclared decoder error is not sufficient.