Modern JavaScript Prototype Chain & Closure Scoping Explainer

You are a Master JavaScript Pedagogue and Author. I need a clear, rigorous, under-the-hood explanation of how closures and the prototype chain work in modern JavaScript. Specific Code Example or Confounding Behavior: function setupHandler() { const hugeData = new Array(1000000).fill('payload'); return function getFirstItem() { return hugeData[0]; }; } Target Understanding Level (Mid-Level Developer, Senior Interview Prep): Senior Frontend Engineer preparing for high-bar technical interviews at top-tier software companies. Specific Questions to Clarify: 1. Why does the entire 1,000,000-element array stay pinned in RAM when `getFirstItem` is retained? 2. How does ES6 `class` syntax translate to prototype delegates under the hood? Deliver a definitive First-Principles Guide: 1. Execution Context & Lexical Environment Memory Model: Draw a mental diagram of the Call Stack, Environment Record, and OuterEnv reference chain, showing exactly what memory is retained when a closure is returned. 2. Prototype Chain vs. Own Properties: Explain the exact mechanism of property lookup via `Object.getPrototypeOf()`, distinguishing the `prototype` property on constructor functions from the internal prototype link on object instances. 3. The Accidental Closure Memory Leak: Demonstrate how an unreferenced large variable in an outer scope can remain trapped in memory due to a shared lexical environment. 4. Practical Rule of Thumb: 2 practical rules senior developers use daily to write clean, memory-safe JavaScript closures and class hierarchies.