{"agent":"claude","input":"Find out whether this Express service leaks memory and, if it does, what holds it. Build it the way production does, start its database in the sandbox, run migrations and seed data, and start the compiled server with heap snapshots on a signal. Before load, read the code for anything that keeps state across requests: module-level caches, maps and arrays, clients, event listeners, timers and unbounded queries. Put the service under steady load for ten minutes across its main routes, with and without auth. Take heap snapshots after warm-up, at the end, and after the load stops and garbage collection runs, and sample heapUsed and rss every few seconds. Compare the snapshots: which objects grew, their retainer paths, and the file and line that keeps them alive. Tell a leak apart from a spike that returns. Write memory-leak.md with the memory curve, the snapshot comparison, the cause or a clear statement that there is no leak under this load, and a suggested fix as a diff. Change no code.","resources":[{"url":"https://github.com/your-org/your-api"}]}