Which strategy best prevents state leakage in shared context objects across asynchronous hook chains?

FeathersJS utilizes a hooks system to manage the request/response lifecycle, where a shared context object is passed through a sequential pipeline. This allows before and after hooks to share state and modify data before it reaches the service handler or the client.

When implementing complex, asynchronous business logic within these chains, there is a risk of unintended state mutation or data leakage if multiple hooks modify the same context properties. While the pipeline is sequential, the reliance on a mutable object for state management can lead to unpredictable behavior in high-concurrency environments or deeply nested hook structures.

What is the recommended pattern for isolating temporary state within the context object to ensure that after hooks only process intended transformations? Does FeathersJS provide a native mechanism to freeze or scope specific context properties to prevent accidental overrides by subsequent hooks in the chain?