check / check (push) Successful in 2m15s
The case where the client stops sending halfway answers 504 only if, when the request timeout runs out, smallwebwaf has not yet connected to the app and passed on the first bytes: until then it is waiting on the app, and SPEC.md asks for 504. That normally takes a few milliseconds of the 300 ms timeout, so the failure needs the test process to be held up for about 300 ms at the start of the request; a pause injected there reproduces it exactly. The code is right, and the test could only gain margin from a longer timeout, which the issue rules out. The comment records this for the next reader. Judgement call: no change to the code or to what the test checks. Model: opus-5-5