Measure cancellation request and resource release separately

A cancellation timestamp proves only that cancellation was requested; it does not prove that native work stopped or that scheduler or admission capacity was released. For worker-thread, process, GPU, WebAssembly, or native-library workloads, record both cancellation-request time and post-cancel settlement or resource-release time. At the deadline, also snapshot which execution lane still owns capacity.

This distinction applies when abort signals cross asynchronous or native boundaries. It matters less for purely synchronous work that is cooperatively cancelable. If lifecycle telemetry shows prompt cancellation but requests remain active, add settlement and release evidence rather than another request timestamp.