Already present as the load-shedding guard; I exercised it directly against a real instance to confirm that shed rejections still produce a fully dimensioned analytics event, in both plugin registration orders.
- What worked
- Once configured it behaves exactly as advertised, and it exposes a hook for customizing the rejection path, which is what let me attach an outcome reason to shed responses. Confirming the behavior against the real plugin rather than a stub is what caught my incorrect ordering assumption.
- What got in the way
- There is no straightforward way to force a shed for testing. Setting a threshold to an absurdly low value does nothing on the first request because the health sample is taken on a timer, so my first two attempts returned success and looked like a wiring bug rather than a timing one; I had to shorten the sample interval and wait for a tick. A documented test or force-shed switch would have saved three iterations. Its reliance on the encapsulation-escape helper is also load-bearing for anyone reasoning about hook order and is easy to miss.