flake class 10 residue OUTSIDE the #111 pin: tests/edge/test_e2e_edge.py:369 asserts 'elapsed < 3.0' over 60 real HTTP round-trips through Docker+Envoy, as a proxy for 'all 60 landed inside one rate-limit window'. #111's in-process clock pin CANNOT reach it — the limiter there is Envoy's http_local_rate_limit filter in a SEPARATE process, not a Python class, so there is no init to wrap and no injectable now. The causal replacement is to read Envoy's own counter instead of the wall clock: GET the admin /stats endpoint and assert http_local_rate_limit.rate_limited equals 60 - max_tokens, which is a fact about the filter rather than a bet on network speed. Deferred, not forgotten: the edge suite is dispatch-only (make e2e-edge), has never run under -n 12, and reaching Envoy admin from the test needs a port publish in infra/docker-compose.edge.yml — a real change in a suite that is not part of the default gate. Until then the site stays explicitly marked NOT MEASURED rather than given a fabricated margin.
Carried from the ADD 2.x bundle (.add/state.json todo #116, captured 2026-08-11T14:57:35+00:00) when the project moved to ADD 3.x, whose worklist is derived from task nodes and has no free-text capture.
⚠ The #116 above is the ADD todo id, not a GitHub number — commit messages, PR bodies and memory notes across this project cite it. This issue's own GitHub number is unrelated.
The byte-identical 2.x record lives in .add-2x-archive/.
flake class 10 residue OUTSIDE the #111 pin: tests/edge/test_e2e_edge.py:369 asserts 'elapsed < 3.0' over 60 real HTTP round-trips through Docker+Envoy, as a proxy for 'all 60 landed inside one rate-limit window'. #111's in-process clock pin CANNOT reach it — the limiter there is Envoy's http_local_rate_limit filter in a SEPARATE process, not a Python class, so there is no init to wrap and no injectable now. The causal replacement is to read Envoy's own counter instead of the wall clock: GET the admin /stats endpoint and assert http_local_rate_limit.rate_limited equals 60 - max_tokens, which is a fact about the filter rather than a bet on network speed. Deferred, not forgotten: the edge suite is dispatch-only (make e2e-edge), has never run under -n 12, and reaching Envoy admin from the test needs a port publish in infra/docker-compose.edge.yml — a real change in a suite that is not part of the default gate. Until then the site stays explicitly marked NOT MEASURED rather than given a fabricated margin.
Carried from the ADD 2.x bundle (
.add/state.jsontodo #116, captured 2026-08-11T14:57:35+00:00) when the project moved to ADD 3.x, whose worklist is derived from task nodes and has no free-text capture.⚠ The
#116above is the ADD todo id, not a GitHub number — commit messages, PR bodies and memory notes across this project cite it. This issue's own GitHub number is unrelated.The byte-identical 2.x record lives in
.add-2x-archive/.