// What the workspace and the server hold in memory, as a person uses HUD: // three canvases of 8 to 10 tiles each (big feeds of posts with pictures, // link cards and videos, a thread, profiles, galleries, documents, a // playlist), the big feeds scrolled five pages each, every tab switched to // twice, then 200 tool calls over MCP. After each stage it prints the // page's JS heap, its DOM nodes and listeners, the pictures and players it // holds, the renderer's image memory as Chromium's memory-infra counts it, // and the server's RSS. Not part of `just e2e`. // // just memory [label] the release build, this scenario; the numbers // also go to target/memory/