KrakenJS Routing Layer and HTTP Server Boot Sequence Interoperability

Goal: Verify whether KrakenJS guarantees that all routes and services are fully registered before the underlying HTTP server starts accepting connections.

During the framework’s boot sequence, the Express application is assembled and the HTTP server is bound to a port, but the automatic discovery of controllers and services can involve asynchronous initialization (e.g., loading configuration files or plugin modules). This creates uncertainty about the exact point at which the server begins listening relative to the completion of route registration.

• At what stage in the boot script does KrakenJS invoke server.listen (or equivalent) relative to the completion of the controller‑loading phase?
• Does the framework provide any explicit hook or event that signals when route registration is finished, allowing developers to defer server start?
• If the server can start before async service initialization finishes, what are the documented guarantees—or lack thereof—regarding request handling during that window?