What problem does it solve? Before committing changes to Nodefony's HTTP pipeline, DI container, or framework core, you need to verify they do not introduce memory leaks. This Skill runs the dedicated Vitest memory gate for @nodefony/http and, crucially, tells you how to interpret the results: which heap thresholds matter, what a breach means, and where to look for the leak. ## Core Features & Use Cases - Memory Gate Execution: Runs the memory.test.ts suite (1000 sequential GETs, 100 sync/async crashes, 100 WebSocket connections) with filtered output showing only heap deltas and failures. - Threshold Interpretation Grid: Maps each test to its critical heap limit (e.g., 1000 GETs < 35 MB, WS connections < 30 MB) and the probable leak cause when exceeded. - Blocker Protocol: Treats any threshold breach as a commit blocker and guides investigation via git diff, listener cleanup checks, and lazy allocation review. - Use Case: After modifying the request pipeline in @nodefony/framework, run this gate before committing; if the sync-crash test exceeds 10 MB, the Skill directs you to check scope cleanup in the Kernel rather than committing a regression. ## Quick Start Ask the assistant to run the Nodefony memory health check against the running server and report whether all heap thresholds pass.
