A process-wide plugin caches task context before transforming system messages, while multiple root and child sessions run concurrently. The design question is how to prevent cross-session context leakage and keep memory bounded. The key unknowns are the cache ownership model, lifecycle signals for roots and children, concurrency guarantees, and whether context can be safely evicted or redacted. This is a reasoning discussion only; no repository or environment inspection has been performed.