Joseph Ferano
6de6c079b0
Two lanes were sent after a contention race on a socket path. There is none. The sentence came from three sites and not the two HANDOFF-f1.md named — test_dev.ml:77 checks the *dev* socket with exactly that wording, in the same block whose *agent* socket check was fixed — and the cause is a bound too short for a build: flan dev links the whole program before it binds, ~600ms warm, measured at 6.5s here and 6.6-6.8s by the lane that fixed it, against a 5000ms await in test_dev.ml and 8000ms in the other two. Build.cachedir sits under dune's per-run TMPDIR, so that build is cold on every invocation and the failure is not occasional at all. The fix landed on another branch; nothing in this commit touches a test. The agent.sock ordering fix it does confirm: 30 sequential full dune test runs, 0 failures, no "never bound" in any log — so NEXT.md's "One flaky test, measured rather than suspected" section, left standing for whoever confirmed it, goes. HANDOFF-f1.md's "lengthening any timeout" bullet is qualified rather than deleted. It was true of the agent.sock check and read as a rule, and reading it as a rule is what kept this open for a second lane.
