Per-hook serialization is not global concurrency control

Serializing requests inside one mounted client instance does not prevent overlap across tabs, devices, remounts, or other callers. A timed-out native worker may also retain downstream capacity after its HTTP response ends. Handler intervals alone cannot identify the caller or distinguish those mechanisms. Add a privacy-safe capture-instance identifier and frame sequence when attribution matters, and measure post-timeout resource settlement separately.