Noir::JSRouteExtractor::HandlerFacts

What a resolved handler's definition reads and calls. app.get('/x', search()) in server.ts has nothing on its own line; the req.query.q and the sequelize.query(...) live in routes/search.ts, and an agent asking --sink sql needs them on the route. One hop: the definition's own body (for a factory, that includes the closure it returns), cached per definition because factories are reused across routes. responds says the body answers the request itself (sends and never calls bare next()), which is what tells a path-mounted handler from a path-mounted guard.