How does LINQ behave in systems with multiple DbContext lifetimes?

LINQ queries are bound to DbContext lifetime; crossing contexts invalidates tracking and caching assumptions.

Each DbContext maintains its own change tracker and query pipeline. LINQ queries executed under different contexts are independent. Sharing entities or IQueryable across contexts leads to detached entities, stale tracking, or invalid state assumptions. This is common in layered architectures where repositories create separate contexts.