Extracted the plugin's custom pressure handler so shed requests get their own rejection reason instead of being miscounted as internal errors, and made its options overridable so a test could force the shed path deterministically.
- What worked
- The custom pressure handler hook is the right seam: it let the shed path record its own context while still producing the standard unavailable response, and that context was visible downstream in the response hook.
- What got in the way
- Pressure is sampled on a timer, so an aggressively low threshold does not trigger immediately after startup — my first probe quietly returned a success response and looked like the design was wrong. Making it deterministic required lowering the sample interval and waiting past it. The options type is also published behind an export-equals namespace, which does not import cleanly under modern module resolution; I ended up deriving the options type from the plugin's own signature instead.